Loading...
Loading...
Found 42 Skills
Authoritative reference for Anthropic products. Use when users ask about product capabilities, access, installation, pricing, limits, or features. Provides source-backed answers to prevent hallucinations about Claude.ai, Claude Code, and Claude API.
Creates PRDs and plans features.
Generate a README introduction following the Diataxis 4-paragraph structure for product documentation.
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
Create, update, validate, or analyze a PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD.
Help users write high-quality Product Requirements Documents (PRD) from scratch, or evaluate/improve existing requirement documents. It is suitable for non-product manager users in vibe coding scenarios who have product ideas but don't know how to structure them. This skill must be used when users mention keywords such as "requirement document", "PRD", "product requirement", "functional document", "I want to make a product/function/App", "help me organize requirements", "is there any problem with the AI-written requirement document", "help me supplement requirements", "I want to make a tool", etc. Even if the description is very brief, this skill must be triggered, and do not skip directly to outputting the document.
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over time in a Decision Trace. For implementing code against a Product Spec that already exists, use the productspec skill instead.
Creates a new Product Requirements Document (PRD) with auto-numbered filenames in the project's PRD directory. Gathers business context, defines the problem, and produces a structured PRD.
Writes and reviews native-quality Vietnamese (vi-VN) engineering and product documentation — commit messages, PR descriptions, code review, RFCs, design docs, postmortems, runbooks, READMEs, API docs, UI and error microcopy, i18n resource files, PRDs, user stories, release notes, changelog entries, in-app notifications, help-centre articles, surveys and research guides, and app-store listings. Use when drafting or reviewing Vietnamese technical or product content, deciding which English terms stay English, choosing the impersonal register over bạn, or handling vi-VN i18n hazards like string expansion, ICU plurals, collation, and NFC. Fixes the machine-translation tells Vietnamese engineers notice immediately.
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
This skill should be used when the user asks to "create a PRD for Replit", "write product requirements", "document app specifications", "prepare a product spec", or needs a comprehensive specification document that Replit Agent can use for complex, multi-feature applications. Creates structured PRDs optimized for AI-powered development.