Total 52,213 skills, Documentation & Writing has 1490 skills
Showing 12 of 1490 skills
Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide.
Creative writing project architecture — concept mapping, thematic structure, outlining, and strand interweaving. Helps the user see the shape of their project. Use when structuring a new project, reorganizing an existing one, or mapping how narrative, art-as-code, and theory interweave.
Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.
Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.
Use when writing or reviewing k6 documentation across TypeScript types, user docs, and release notes.
Rules and worked examples for writing prose that does not read like AI-generated slop. Consult before writing or editing any prose.
Evaluate and score film and television scripts from three dimensions: ideological value, artistic merit, and viewability. Suitable for quality assessment during script development, determining revision directions, and pre-project approval review.
문서 내부 또는 프로젝트 전체에서 일관된 작성 스타일을 유지하도록 돕는 검사기. 어조(경어체/반말), 용어(사용자/유저), 숫자 형식, 목록 스타일, 따옴표, 날짜/시간 형식의 불일치를 감지합니다. 다중 작성자 문서 검토 시, 프로젝트 전체 용어 표준 유지 시, 공식 문서 준비 시, 브랜드 일관성을 위한 문서 작업 시 사용하세요.
Use when reviewing React documentation for structure, components, and style compliance
Diagnose world-level story problems. This skill should be used when settings feel thin, institutions feel designed rather than evolved, economies don't make sense, or non-human species feel like humans in costume. Keywords: worldbuilding, setting, world, institutions, economy, culture, species, consequences.
This skill should be used when the user asks to "write SDK examples", "create a changelog", "release notes", "developer documentation", or mentions API examples or technical product updates. Creates clear, actionable developer resources and product communication.
Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.