agentsclimarketplace

Docs & writing

16,621 rows, by stacks then stars

3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid

  • Simplify docs

    MAHDTech/agent-skills/skills/writing/simplify-docs Skill

    0★ repo

    Simplify documentation for clarity and readability with approval-gated edits. Use when asked to simplify, rewrite, restructure, or de-clutter a doc — README, setup guide, reference or technical documentation — so it scans faster and leads with the shortest successful path.

  • Strategy translate

    lucaswychan/quant-paper-agent/.agents/skills/strategy-translate Skill

    0★ repo

    Translate a user-accepted quantitative replication into a framework-specific event-driven strategy and equivalence tests. Use only after a replication benchmark is complete and explicitly accepted, and when a schema-valid framework contract defines events, strategy callbacks, orders, fills, positions, contract metadata, risk limits, and clock semantics. Produces research or paper-trading code by default; live deployment requires separate operational review.

  • Strategy translate

    lucaswychan/quant-paper-agent/quant_paper_skills/skills/strategy-translate Skill

    0★ repo

    Translate a user-accepted quantitative replication into a framework-specific event-driven strategy and equivalence tests. Use only after a replication benchmark is complete and explicitly accepted, and when a schema-valid framework contract defines events, strategy callbacks, orders, fills, positions, contract metadata, risk limits, and clock semantics. Produces research or paper-trading code by default; live deployment requires separate operational review.

  • Summarize anything

    biyearly-mesothelioma790/skills/summarize-anything Skill

    no license0★ repo

    Summarizes arbitrarily long text (1k-1M words) using recursive map-reduce with any LLM backend. Accepts raw text, markdown, transcripts, articles, codebases, or any plaintext input. Produces one or more output formats: executive summary, section headings with timestamps, YouTube description, Twitter/X posts, title options, thumbnail prompts, blog outlines, pull quotes, and more. Supports focus directives ("focus on the AI parts", "emphasize the business angle") to steer the summary. Pluggable backends: OpenRouter, Ollama, OpenAI, Anthropic, Gemini, or any OpenAI-compatible endpoint. Use this skill when someone says "summarize this", "give me a summary", "TL;DR", "make this shorter", "create a YouTube description", "write a tweet about this", "generate titles", "thumbnail ideas", or provides long text and wants any condensed output.

  • Adoption report

    h3y6e/agent-skills/.vendor/skills/adoption-report Skill

    0★ repo

    Produce a design system adoption report separating coverage from actual adoption, with trend direction and risk flags. Trigger when someone says: adoption report, how much is the system being used, usage metrics, adoption status, coverage report, which teams are using the system, who's not using the system, or anything about measuring or reporting on how widely the design system is being used. Here 'coverage' means adoption coverage (how much of the system teams actually use). Do NOT trigger for documentation coverage or doc staleness — use docs-coverage for whether the documentation surface keeps pace with the components.

  • Ai component description

    h3y6e/agent-skills/.vendor/skills/ai-component-description Skill

    0★ repo

    Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write component description for AI, Figma MCP description, write the description for Claude to read, six-section description, describe this component for AI, or anything about writing text that makes components legible to LLMs. Do NOT trigger for JSON metadata schemas, structured constraint files, or programmatic tooling data — use metadata-schema-generator for those.

  • Codemod generator

    h3y6e/agent-skills/.vendor/skills/codemod-generator Skill

    0★ repo

    Generate codemods (automated code transformation scripts) for design system migrations — token renames, component API changes, prop deprecations, and import path updates. Produces ready-to-run jscodeshift or custom AST transform scripts that safely apply changes across consuming codebases. Trigger when someone says: generate a codemod, automate this migration, write a transform script, bulk rename tokens, auto-migrate components, jscodeshift for this change, create a migration script, update all imports, rename this prop everywhere, or anything about automating code changes across consumers of a design system. Do NOT trigger for planning the deprecation process — use deprecation-process for that. Do NOT trigger for writing release notes about a change — use change-communication for that.

  • Conventional changelog

    h3y6e/agent-skills/.vendor/skills/conventional-changelog Skill

    0★ repo

    Reference for Conventional Commits and automatic CHANGELOG generation. Compares release-please / changesets / git-cliff / towncrier and covers commit format, Keep a Changelog, and semver tag practices. Use when setting up or unifying a release flow.

  • Docs coverage

    h3y6e/agent-skills/.vendor/skills/docs-coverage Skill

    0★ repo

    Audit whether a design system's documentation surface keeps pace with its component library — coverage gaps (components with no docs), staleness (docs that predate the component's last code change), and orphaned docs. Works with zero integration from the codebase and a Storybook build; Zeroheight, Supernova, and custom docs sites are optional layers. Trigger when someone says: docs coverage, documentation audit, are our docs up to date, which components are undocumented, is our documentation keeping pace, stale docs check, documentation health, Storybook coverage, or anything about whether the documentation surface matches the components. Do NOT trigger for WRITING documentation — use usage-guidelines, pattern-documentation, token-documentation, or ai-component-description for that. Do NOT trigger for general system health (use system-health) or for documentation usage/analytics (use adoption-report).

  • Documentation and adrs

    h3y6e/agent-skills/.vendor/skills/documentation-and-adrs Skill

    0★ repo

    Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

  • Extract glossary

    h3y6e/agent-skills/.vendor/skills/extract-glossary Skill

    0★ repo

    指定されたリポジトリ、複数リポジトリ、または GitHub organization から、ドメイン固有の専門用語、業界用語、社内・プロダクト用語、リポジトリ実装マップ、技術構成、オンボーディング向け Mermaid 構成図を抽出・生成するときに使う。ユーザーが「用語集を作る」「ドメイン辞書を作る」「オンボーディング資料にする」「repo/org を見て専門用語をまとめる」「AI が再確認しなくてよい知識ベースを作る」と依頼したら起動する。

  • Grill with docs

    h3y6e/agent-skills/.vendor/skills/grill-with-docs Skill

    0★ repo

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

  • Pattern documentation

    h3y6e/agent-skills/.vendor/skills/pattern-documentation Skill

    0★ repo

    Write documentation for a design system pattern — a multi-component recipe covering use cases, anti-patterns, composition, and related patterns. Patterns span multiple components working together (e.g. a form pattern, a data table pattern). Trigger when someone says: document this pattern, write the pattern page, usage pattern, when to use this, pattern guidelines, document how this works, or anything about creating documentation for a reusable UI pattern rather than a single component. Do NOT trigger for writing usage guidelines for a single named component — use usage-guidelines for that.

  • Playwright test

    h3y6e/agent-skills/.vendor/skills/playwright-test Skill

    0★ repo

    Best practices and reference for Playwright Test (E2E). Covers how to write tests, avoiding fixed waits, network triggers, DnD, shard/retry setup on GitHub Actions, and more. Use when writing, reviewing, or configuring CI for Playwright tests.

  • Ponytail

    h3y6e/agent-skills/.vendor/skills/ponytail Skill

    0★ repo

    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

  • Provider docs

    h3y6e/agent-skills/.vendor/skills/provider-docs Skill

    0★ repo

    Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.

  • Research

    h3y6e/agent-skills/.vendor/skills/research Skill

    0★ repo

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

  • Stakeholder brief

    h3y6e/agent-skills/.vendor/skills/stakeholder-brief Skill

    0★ repo

    Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design system status to an audience that does not have a design systems background.

  • Token documentation

    h3y6e/agent-skills/.vendor/skills/token-documentation Skill

    0★ repo

    Write documentation for design tokens — covering semantic intent, usage context, and do/don't examples. Trigger when someone says: document these tokens, token reference, what does this token mean, token usage guide, write the token docs, token intent, or anything about creating human-readable documentation for design tokens.

  • Translate programming language

    h3y6e/agent-skills/.vendor/skills/translate-programming-language Skill

    0★ repo

    Plan and execute language-to-language server or application migrations with behavior parity. Use when porting modules, services, APIs, or runtimes between programming languages; generating source-runtime oracles and fixtures; generating migrated parity tests; detecting runtime, standard-library, serialization, numeric, encoding, time, regex, or protocol differences; building temporary compatibility layers; accumulating migration knowledge; benchmarking; shadow testing; canarying; or planning cutover and rollback.

  • Usage guidelines

    h3y6e/agent-skills/.vendor/skills/usage-guidelines Skill

    0★ repo

    Write usage guidelines for a specific, named component — covering when to use it, when not to, edge cases, and anti-patterns for that one component. This documents HOW to use a component you have already chosen, NOT how to choose between components. Trigger when someone says: write usage guidelines for [component], do's and don'ts for [component], how should [component] be used, usage rules, write the guidelines for [component], or anything about creating prescriptive guidance for a single named component. Do NOT trigger for choosing between components — use component-decision-tree for that. Do NOT trigger for documenting multi-component patterns — use pattern-documentation for that.

  • Visual report

    h3y6e/agent-skills/.vendor/skills/visual-report Skill

    0★ repo

    Generate visual output — charts, dashboards, and trend graphs — from audit findings, session history, or system health data. Produces an interactive HTML dashboard or a set of SVG/Mermaid charts that make design system health visible at a glance. Trigger when someone says: visualise the findings, show me a chart, create a dashboard, graph the trends, make this visual, health dashboard, show me the data, I need charts for the stakeholder meeting, turn this into a visual report, or anything about producing visual representations of design system data. Do NOT trigger for producing a written stakeholder brief without visuals — use stakeholder-brief for that. Do NOT trigger for running an audit — run the audit skill first, then use visual-report to visualise the output.

  • Vitepress

    h3y6e/agent-skills/.vendor/skills/vitepress Skill

    0★ repo

    VitePress static site generator powered by Vite and Vue. Use when building documentation sites, configuring themes, or writing Markdown with Vue components.

  • Writing beats

    h3y6e/agent-skills/.vendor/skills/writing-beats Skill

    0★ repo

    Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

  • Writing fragments

    h3y6e/agent-skills/.vendor/skills/writing-fragments Skill

    0★ repo

    Writing, explore — mine raw fragments, no structure yet.

  • Writing great skills

    h3y6e/agent-skills/.vendor/skills/writing-great-skills Skill

    0★ repo

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

  • Writing guidelines

    h3y6e/agent-skills/.vendor/skills/writing-guidelines Skill

    0★ repo

    Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

  • Writing plans

    h3y6e/agent-skills/.vendor/skills/writing-plans Skill

    0★ repo

    Use when you have a spec or requirements for a multi-step task, before touching code

  • Writing shape

    h3y6e/agent-skills/.vendor/skills/writing-shape Skill

    0★ repo

    Writing, exploit — shape raw material into an article, paragraph by paragraph.

  • Writing skills

    h3y6e/agent-skills/.vendor/skills/writing-skills Skill

    0★ repo

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

  • Writing japanese

    h3y6e/agent-skills/skills/writing-japanese Skill

    0★ repo

    my agent skills

  • Kozen wiki writer

    kozen-labs/agentic/.agents/skills/kozen-wiki-writer Skill

    0★ repo

    Expert guide for producing Kozen module project documentation: GitHub wiki pages, README synchronisation, and GitHub Issues. Covers the full authoring workflow: choosing a publication mode (GitHub Wiki vs docs/ vs tmp/ staging), the Home.md = README.md parity rule (minimal high-level content that works on GitHub, npm, and PyPI), progressive disclosure across the page set, source analysis checklist (entry point exports, CLI help files, IoC configs, package.json), all format conventions (navigation footer, emoji-heading map, PascalCase-hyphen naming, absolute URLs), the no-duplication rule, bibliography and licence/disclaimer structure, and standardised GitHub Issues (title, problem description, location, consequences, reproduction steps, possible solutions) with publication modes for GitHub-managed or docs-managed issue tracking.

  • I18n source of truth

    cristianorj22/arthus-harness/plugins/i18n/claude/skills/i18n-source-of-truth Skill

    0★ repo

    Multi-locale invariants — single source-of-truth file, strict parity, glossary discipline, no string concatenation. Use when adding any user-facing string or modifying locale files.

  • Journey mapping

    cristianorj22/arthus-harness/plugins/journey-mapping/claude/skills/journey-mapping Skill

    0★ repo

    User journey docs in Docs/produto/jornadas/<persona>/<jornada>.md — capture sequence of steps + edge cases + multi-actor handoffs + a11y branches + recovery paths + falha catastrófica. Use when reviewing or writing surfaces that affect user flow (booking, onboarding, plan subscription, payment, cancellation, etc.). When a PR touches a surface that has a journey, ask "this surface change is in jornada X — was the journey updated?".

  • Experience principles

    cristianorj22/arthus-harness/tests/snapshots/full-stack/.claude/skills/experience-principles Skill

    0★ repo

    Preserve experience invariants when reviewing or writing UI / copy / fluxos / mensagens de erro / empty states / loading. Reads `Docs/produto/principios-de-experiencia.md` dynamically — works with whatever sensações + réguas the project defined.

  • I18n source of truth

    cristianorj22/arthus-harness/tests/snapshots/full-stack/.claude/skills/i18n-source-of-truth Skill

    0★ repo

    Multi-locale invariants — single source-of-truth file, strict parity, glossary discipline, no string concatenation. Use when adding any user-facing string or modifying locale files.

  • Journey mapping

    cristianorj22/arthus-harness/tests/snapshots/full-stack/.claude/skills/journey-mapping Skill

    0★ repo

    User journey docs in Docs/produto/jornadas/<persona>/<jornada>.md — capture sequence of steps + edge cases + multi-actor handoffs + a11y branches + recovery paths + falha catastrófica. Use when reviewing or writing surfaces that affect user flow (booking, onboarding, plan subscription, payment, cancellation, etc.). When a PR touches a surface that has a journey, ask "this surface change is in jornada X — was the journey updated?".

  • Experience principles

    cristianorj22/arthus-harness/tests/snapshots/minimal/.claude/skills/experience-principles Skill

    0★ repo

    Preserve experience invariants when reviewing or writing UI / copy / fluxos / mensagens de erro / empty states / loading. Reads `Docs/produto/principios-de-experiencia.md` dynamically — works with whatever sensações + réguas the project defined.

  • Experience principles

    cristianorj22/arthus-harness/tests/snapshots/web-supabase/.claude/skills/experience-principles Skill

    0★ repo

    Preserve experience invariants when reviewing or writing UI / copy / fluxos / mensagens de erro / empty states / loading. Reads `Docs/produto/principios-de-experiencia.md` dynamically — works with whatever sensações + réguas the project defined.

  • Feature doc rubric

    volodymyrkoval/tdd-claude/skills/feature-doc-rubric Skill

    no license0★ repo

    Apply when generating or auditing a feature live-spec — the short, human-readable doc written right after `/done`. Drives a five-section discipline: source of truth, length & tone, required sections, drift sweep across existing docs, and behavior-change verification. Reusable by both feature-documenter (writer) and any future feature-doc-auditor.

  • Ui test rubric

    volodymyrkoval/tdd-claude/skills/ui-test-rubric Skill

    no license0★ repo

    Apply when writing a UI integration test at a component seam, when reasoning about test scope at component boundaries, when deciding what to mock in a UI test, or when an integration test is hard to write — re-check scope. Reusable by both ui-integration-tester (writer) and future ui-integration-auditor (auditor).

  • Humanize documentation

    atkntepe/skillbox/skills/humanize-documentation Skill

    0★ repo

    Use when the user wants to rewrite, review, or improve technical documentation that feels AI-written, stiff, verbose, imprecise, ambiguous, hard to scan, or disconnected from source behavior. Apply to component and API docs, README usage sections, guides, reference tables, migration notes, examples, and troubleshooting content, including requests for Simplified Technical English (STE)-inspired clarity; do not use for pure marketing copy or unsupported rewrites that would require inventing product behavior.

  • Write animation prompts

    atkntepe/skillbox/skills/write-animation-prompts Skill

    0★ repo

    Use when drafting, rewriting, critiquing, or expanding AI prompts for animation, motion design, text-to-video, product demos, UI microinteractions, animated storyboards, kinetic typography, or any request where precise motion vocabulary, timing, easing, sequencing, camera movement, or transition language would improve the result.

  • Write codex goal

    atkntepe/skillbox/skills/write-codex-goal Skill

    0★ repo

    Use when the user wants to draft or revise a Codex `/goal` prompt, goal instruction Markdown file, durable long-running objective, stopping condition, validation loop, checkpoint plan, progress contract, or background-task brief. Apply when work should persist across many turns with measurable completion; do not use for one-off prompts, loose backlogs, or tasks whose next step depends on frequent unresolved product decisions.

  • Cold email writer

    Autter-dev/agentic-sales-skills/02-prospecting-and-outreach/outreach/skills/cold-email-writer Skill

    0★ repo

    Writes personalized cold emails in 3 variant frameworks with subject lines, CTAs, and response rate scoring

  • Golang documentation

    guynhsichngeodiec/cc-skills-golang/skills/golang-documentation Skill

    0★ repo

    Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.

  • File adr

    ultimatile/development-skills/skills/file-adr Skill

    no license0★ repo

    Draft an Architecture Decision Record (a timeless decision, distinct from an implementation schedule) and write the file. Use file-issue instead when the artifact is a task list, bug report, or phase plan.

  • File pubdoc

    ultimatile/development-skills/skills/file-pubdoc Skill

    no license0★ repo

    Draft README.md or visitor-facing markdown (top-level *.md, docs/**/*.md) using the canonical skeleton, complementing the public-doc-durability audit.

    The same file is in 1 other repository

  • Api docs

    xiongxianzhu/xskills/skills/api-docs Skill

    0★ repo

    按项目规范编写 API 文档。使用场景:用户要求写接口文档、补充 API 说明、为第三方或内部接口编写文档时。

  • Patent writer

    palmiro72-coder/palmiros-claude/plugins/palmiros-research/skills/patent-writer Skill

    0★ repo

    Redige patentes e documentação técnica conforme INPI e PCT. Analisa invenções, gera reivindicações. Suporte Lei do Bem para incentivos fiscais de P&D.

  • Doc feat desc

    lencamo/skills/skills/doc-feat-desc Skill

    0★ repo

    Use when the user wants user-facing docs for an implemented feature. Inspect the real implementation first, then write help-center, site-copy, and in-product docs under `doc/{requirement-name}/`.

  • Defuddle

    sonhaicoder/haiclaudeskill/skills/obsidian-skills/skills/defuddle Skill

    0★ repo

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.

    The same file is in 6 other repositories

  • Obsidian markdown

    sonhaicoder/haiclaudeskill/skills/obsidian-skills/skills/obsidian-markdown Skill

    0★ repo

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

    The same file is in 15 other repositories

  • Memo

    rerelurelu/skillbox/skills/memo Skill

    0★ repo

    セッション中に得た技術知識・設計判断・ドメイン知識・ユーザーのコーディングのクセ・長所・苦手を知識倉庫 (~/dev/knowledge、Obsidian vault) に記録する。次のイベントの直後に必ず使う: コミットした直後、PR をマージした直後、レビュー指摘への対応が完了した直後、設計判断が確定した直後、非自明な挙動やハマりの原因が判明した直後、ユーザーの良い判断・つまずき・傾向を観測した直後。また「メモして」「記録して」と言われたときに使う。

  • Latex sentence per line

    jacobleft/techang/skills/latex-sentence-per-line Skill

    no license0★ repo

    Use when writing, revising, or polishing prose in LaTeX `.tex` files and you want one sentence per line, especially for thesis sections, paper sections, manuscript prose, or any workflow where edited LaTeX prose should be normalized before completion.

  • Wittgenstein authoring

    jacobleft/techang/skills/wittgenstein-authoring Skill

    no license0★ repo

    Audits and revises reader-facing prose for agentic writing failures: defensive negation/此地无银, source-term leakage, unstable naming, weak structure, logic jumps, and overclaiming. Use when the user asks to revise prose, translate notes/code/reviews into prose, diagnose AI-like or suspicious writing, stabilize terminology, analyze structure rather than content, or enforce silence at exposition boundaries.

  • Fix prose

    rysk-tanaka/skills/skills/fix-prose Skill

    0★ repo

    コードコメント・ドキュメント内の語彙や言い回しを辞書ルールに従って自動で直す (user)

  • Pdf to markdown

    sujithq/skills/skills/pdf-to-markdown Skill

    0★ repo

    Converts PDF files to Markdown using Microsoft's markitdown package. Use this skill when the user asks to convert a PDF to Markdown, extract text from a PDF, or read/parse PDF content.

  • Google style cpp

    sanjeevafk/agent-skills/skills/google-style-cpp Skill

    0★ repo

    Apply Google's official C++ style guide when writing, reviewing, or formatting C++ code. Use this skill whenever the user asks to review C++ for style, asks about C++ naming conventions, header organisation, smart pointer usage, exception policy, template guidelines, or whether code follows Google C++ standards. Also triggers on: "is this idiomatic C++?", "clean up this C++ file", "how should I name this in C++?", "should I use exceptions in C++?", "how do I write C++ comments / Doxygen?", "should I use auto here?", "when should I use references vs pointers?", or any mention of clang-format, cpplint, or IWYU in a Google-style context. Note: Google's C++ guide is deliberately conservative — it restricts several modern C++ features (exceptions, RTTI, some template meta-programming) for reasons of build reproducibility and readability at scale.

  • Google style java

    sanjeevafk/agent-skills/skills/google-style-java Skill

    0★ repo

    Apply Google's official Java style guide when writing, reviewing, or formatting Java code. Use this skill whenever the user asks to review Java code for style, asks about Java naming conventions, import ordering, annotation placement, Javadoc format, brace style, or whether code follows Google Java standards. Also triggers on: "is this idiomatic Java?", "clean up this Java file", "how do I write Javadoc?", "should I use this Java pattern?", "what's the Google way for Java exceptions?", "how should I format this Java class?", or any mention of google-java-format, Checkstyle in a Google-style context. Note: this guide covers Java; for Kotlin use the Kotlin style guide; for Android Java also check Android-specific rules.