Loading...
Loading...
Found 2,062 Skills
Write PRDs, specs, and project context optimized for coding assistants (Claude Code, Cursor, Copilot, Custom GPTs). Includes CLAUDE.md generation, session planning, and templates for creating documentation that tools can execute effectively.
Creates task management documentation (docs/tasks/README.md + kanban_board.md). L2 Worker in ln-100-documents-pipeline. Sets up Linear integration and task tracking rules.
[Utilities] Convert markdown files to Microsoft Word (.docx) with custom styling. Use when generating Word documents from markdown, creating editable documentation, or exporting reports for Microsoft Office.
arc42 architecture documentation template and guidance
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
Guidelines for creating and modifying markdown files. Use when writing documentation, README files, or any markdown content.
Conducts in-depth analysis of a specific source or topic, producing comprehensive summaries for research synthesis. Use when you need detailed analysis and documentation of individual sources as part of a larger research effort.
Generate a Phase Spec/PRD by extracting features from an annotated Vision PRD. Use when user wants to create quarterly phase documentation, extract requirements from vision, plan a development phase, or decompose features into R-nnnn requirements. Requires annotated Vision PRD with F-nnn tags and Coverage Index.
Searches and retrieves MLflow documentation from the official docs site. Use when the user asks about MLflow features, APIs, integrations (LangGraph, LangChain, OpenAI, etc.), tracing, tracking, or requests to look up MLflow documentation. Triggers on "how do I use MLflow with X", "find MLflow docs for Y", "MLflow API for Z".
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. Use when authoring or reviewing content in adev/src/content.
Technical writer specializing in the Diátaxis documentation framework
Initialize a long-running project with a structured docs workflow, or update an existing project (new features, bug fixes, refactors, requirement changes). Use this skill whenever the user wants to start a new project, kick off a long-running build task, set up project documentation structure, or says things like "new project", "start a project", "init project", "project setup", or "I want to build something from scratch". Also use when the user mentions wanting a milestone-based plan, structured execution workflow, or asks to scaffold documentation for a complex multi-step build. Additionally, use this skill when the user wants to modify an existing project that already has a `docs/` directory — e.g., "add a new feature", "fix this bug", "refactor X", "I want to change how Y works", "new feature request".