Technical Writing

Analyze and optimize markdown documents for size, structure, and maintainability.Use when: (1) markdown files are too large or verbose, (2) documentation needsrestructuring, (3) checking docs for quality issues, (4) converting prose to tables.

Write valid XHTML-strict HTML5 markup. Use when creating HTML files, editing markup, building web pages, or writing any HTML content. Ensures semantic structure and XHTML syntax.

Use this skill when writing Go code following the Uber Go Style Guide. Provides comprehensive guidance on idiomatic Go patterns, error handling, concurrency safety, performance optimization, and test-driven development. Covers all critical Uber Go rules including channel sizing, goroutine management, interface design, and proper error handling. Appropriate for any task involving .go files, Go code reviews, refactoring, or implementing Go best practices.

Applies project-specific coding conventions and patterns. Use when writing, reviewing, or modifying code to maintain consistency with the codebase style.

Generate documentation for CCAGI system components, architecture, and workflows. Use when documenting features, updating architecture docs, or explaining how components work.

Formats markdown files according to best practices and common style guidelines. Use when cleaning up markdown documentation, ensuring consistent formatting, or standardizing README files.

Documentation organization, maintenance, and cleanup.USE WHEN: organizing docs, cleaning project root, updating documentation,checking for redundancy, maintaining docs structure.NOT FOR: technical implementation (use relevant technical skill).Examples:<example>Context: User added documentation to wrong location.user: "I added a new API doc file to the root directory"assistant: "I'll use docs-keeper to organize it in the proper docs/ location."<commentary>File organization is docs-keeper responsibility.</commentary></example><example>Context: User needs to update docs after code changes.user: "I modified the auth system and need to update the docs"assistant: "I'll use docs-keeper to update the authentication documentation."<commentary>Documentation updates are docs-keeper responsibility.</commentary></example>

Write content following Replit's brand voice and style guidelines. Use when creating or reviewing any user-facing content including changelogs, documentation, or marketing materials. Ensures consistent professional yet approachable tone.

Standards for project scaffolding, directory structure, and initial documentation.

Implement testing patterns for PhotoVault using Playwright and Vitest. Use when writing E2E tests, unit tests, API route tests, or debugging flaky tests. Includes PhotoVault test fixtures, page objects, and Stripe webhook testing patterns.

Systematically analyzes and fixes GitHub CodeQL security alerts with proper documentation and testing

This skill should be used when the user asks about "steering documents", "project steering", "workflow setup", "CLAUDE.md configuration", "AGENTS.md", "AI agent project setup", or needs to understand how to configure steering documentation for AI-driven development workflows.

Creating Storybook documentation with proper stories, argTypes, model instances, and variations

Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment

Use this skill when working with OpenStudio 3.10 .osm models to adjust HVAC systems, equipment, thermal zones, schedules, or constructions, then run simulations to validate changes. Handles applying existing measures, running CLI simulations, and saving versioned model files. Delegates to diagnosing-energy-models for simulation failures and writing-openstudio-model-measures for custom measure creation. Includes BCL measure search and download.

Use PROACTIVELY when creating, reviewing, or updating Claude Code Skills. MUST be invoked before writing any new SKILL.md file. Provides structure, workflows, and validation for skill development.

Initialize a fork of GoodDocs with fork-specific defaults and a customized doc type.

This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.

Automates new project setup from the software-dev-project-template including customization, documentation generation, and initial sprint planning

Build complete features with Server Actions, forms, Zod validation, database CRUD operations, and comprehensive tests. Use when user requests "add a feature", "build a [feature]", "create [feature] with forms", or needs end-to-end implementation with validation and testing. Scaffolds pages, actions, schemas, loading/error states, and unit/integration/E2E tests. Supports multi-step wizards, image uploads, markdown editing, custom JSON attributes, and relationship management. Do NOT use for simple static pages (use worldcrafter-route-creator), database-only changes (use worldcrafter-database-setup), testing existing code (use worldcrafter-test-generator), or auth-only additions (use worldcrafter-auth-guard).