documentation-standards
How user-facing and internal documentation should be written and maintained.
Discover Development skills, compare source repositories and read the instructions for each workflow.
How user-facing and internal documentation should be written and maintained.
Standards for security documentation and writeups
Design API endpoints, schemas, and contracts. Use when defining public interfaces or data models.
Cross-check design artifacts for consistency and completeness. Use before implementation.
Scan code for security vulnerabilities. Use after implementation changes.
Review code for style, performance, and maintainability. Use before merging changes.
Create isolated git worktrees for ALL coding tasks with issue linking (discovery: implementation-clarity). Evaluate at implementation-clarity when task modifies code files. YOU MUST use for feature development,...
Extract and read Claude conversation JSONL files with composable filters (discovery: rubber-duck). Evaluate at rubber-duck or at any point in the sesssion when task requires reading conversation history, verify...
Create GitHub Issues for client deliverables in DaveX2001/deliverable-tracking repo (discovery: rubber-duck). Evaluate at requirements-clarity when user mentions tracking, deliverables, commitments, or 'create...
Implement or review frontend features in this repo using Next.js App Router, React Server Components by default, Tailwind, and TypeScript. Use when changing UI, components, routes, or frontend architecture unde...
Repo-wide rules, task workflow, and quality gates for this portfolio project. Use at the start of any task or when making cross-cutting decisions.
Architecture and code review guidance for this repo, with RSC boundaries, SOLID, quality gates, and mentoring. Use when reviewing changes or advising design.
Deployment and infra guidance for this repo. Use when deciding deployment strategy, environment setup, or future infra readiness (Vercel now; AWS/K8s later).
Testing strategy and implementation for this repo using Jest and TypeScript. Use when writing, reviewing, or planning unit, integration, or future E2E tests.
Authoritative guide on Next.js 16+ App Router structure. Use this skill to determine where files should be created, how to name them for routing, and how to organize project architecture.
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the...
Use this skill whenever the user wants to set up, improve, or run frontend tests (unit, component, and E2E) for a Next.js (App Router) + TypeScript + Tailwind + shadcn/ui project using Vitest/Jest, React Testin...
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Strictly enforces Prisma 7 + Next.js App Router protocols. Manages the lifecycle from initialization to deployment. Use for all database tasks.
Maps and documents the codebase. Generates `docs/CODEBASE_MAP.md` with architecture diagrams, module relationships, and data flow. Use when the user asks to "map the code", "explain the architecture", or "updat...
Initialize a new repository with standard scaffolding - git, gitignore, CLAUDE.md, justfile, mise, and beads. Use when starting a new project or setting up an existing repo for Claude Code workflows.
Expert Rust developer specializing in ownership semantics, zero-cost abstractions, and idiomatic patterns. This skill should be used PROACTIVELY when working on any Rust code - implementing features, debugging...
Apply data-oriented architecture patterns when designing systems with polymorphic entities. This skill should be used PROACTIVELY when encountering switch statements or if/else chains that dispatch based on ent...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation before any fix attempts. Random fixes waste time and create new bugs.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.