Document Next.js and Convex code with per-file summaries and data flows.
npx skills add https://github.com/Posteriot/makalah-app --skill docs-writer-posteriot
Please help me install this Agent Skill. Skill: docs-writer Source: https://github.com/Posteriot/makalah-app/tree/main/.codex/skills/project/docs-writer Command: npx skills add https://github.com/Posteriot/makalah-app --skill docs-writer-posteriot
This Skill ensures that every documentation request is grounded in the actual codebase by delivering a high-level explanation backed by file-specific insights, so teams avoid vague assumptions and get precise implementation context.
Request a documentation summary covering the target files and their data flows to activate this Skill.
High-intent search queries and answers about installing and using this skill.
You document Next.js code structure by mapping dependencies, noting data flows, and listing related files to produce a high-level summary backed by per-file walkthroughs. This grounds the documentation in the actual codebase, avoiding vague assumptions.
Writing technical documentation for Convex endpoints involves reading the actual source files and mapping data hooks before crafting explanations. This delivers precise implementation context by covering purpose, data flow, dependencies, and edge cases for both high-level and detailed consumers.
Yes, you can generate per-file implementation details by reading source files and applying a provided style template. The process maps dependencies and notes edge cases, ensuring the walkthroughs maintain concise clarity for detailed consumers.
Documenting both high-level features and detailed code flows works by producing a structured overview alongside file-specific insights. The method highlights the intended strategy for linking components and covers data hooks, props, and related files according to style templates.
Mapping dependencies before writing codebase documentation is necessary to ground explanations in actual implementation details. This ensures summaries and per-file walkthroughs accurately reflect data flows, edge cases, and related files instead of relying on vague assumptions.
Sir-chawakornGenerate and maintain project documentation from source code and git history.
sg6724Save markdown content into .md files with a content string and output filename.
udecodeGenerate Convex-backed type-safe APIs with cRPC hooks for React apps.
zenobi-usAutomate API documentation creation and maintenance with OpenAPI integration.
