Comprehensive construction documentation skill covering architectural drawing sets, sheet organization and numbering, drawing standards (line weights, text, hatching, dimensions), BIM Level of Development (LOD) requirements, specification writing using CSI MasterFormat, schedule production (door, window, finish, fixture), and construction administration workflows including RFI processing, submittal review, change orders, site observations, punch lists, and warranty period management.
2917mo agoReviewMountCreate a free account to mount
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.
Authors and reviews business-facing documentation for analytical models and columns. Use when adding or improving model or column descriptions, documenting grain, keys, measures, dimensions, null semantics, lineage, or docs blocks; when resolving stale or copied descriptions; or when build-model needs documentation for a model.
Audit Station documentation, READMEs, architecture diagrams, and code comments against implementation and behavior evidence; maintain the learning path when features change. Use for documentation audits or feature changes that alter a documented journey or contract.
Use before creating, expanding, or revising any AI-consumed documentation artifact (spec, decisions, tasks, verification-gate, handoff, backlog, problem-catalog, product/business-logic docs, project-internal skills). Classifies whether a persistent doc is needed, which tier applies, and how to minimize context cost. Operationalizes FR-23 — documentation budget. Prevents duplicate rationale, narrative padding, and docs created merely because a template exists. Do NOT use for operator chat, source comments (that's `comment-policy`), or purely human-facing files (README/LICENSE/PUBLISHING).
Synchronize bilingual documentation when StaticPHP v3 user-facing or developer-facing documentation must change. Use when adding, modifying, deprecating, or removing documented features, CLI commands/options, environment variables, configuration formats, public APIs/extension points, workflows, installation requirements, migration guidance, or user-visible behavior. Do not use solely for internal implementation changes, package/library additions, or build bug fixes unless they change documented behavior or require updating existing docs.
Steady7 mentions in 2 weeks
No other project uses it yet
2k3mo agoReviewMountCreate a free account to mount
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
2710mo agoReviewMountCreate a free account to mount
Create or update component documentation in Sentry's MDX stories format. Use when asked to "document a component", "add stories", "write component docs", "create an mdx file", "add a stories.mdx", or document a design system component. Generates structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types.
46k4mo agoReviewMountCreate a free account to mount
Use when porting documentation from Skia C++ headers to Rust APIs, including Rustdoc comments, parameter descriptions, type links, or C++-to-Rust names.
No other project uses it yet
1.8k7d agoReviewMountCreate a free account to mount
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Use when the user asks for a documentation review, doc audit, doc comment review, godoc review, proto comment review, OpenAPI or Swagger spec review, README review, example test review, "are the docs in sync with the code", "do the docs still match", "are these comments accurate", or "check the examples". Also use when another skill dispatches a documentation review.
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.
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.
Skill: Documentation
## Propósito
Generar documentación de calidad para el código: docstrings, JSDoc, README sections, comentarios técnicos y documentación de API.
## Cuándo activar este skill
- El usuario pide "documentar", "documentación", "docstrings
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
AbhinavbwjSkill
