Technical Writing

命名规范 / Naming conventions。在创建类、函数、变量，或重命名、检查命名时使用。核心原则：简洁优先，上下文消歧义，类型提示已提供足够信息。Use when naming classes/functions/variables, renaming code, or reviewing names. Prioritizes brevity over self-documentation.

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

Prepare manuscripts for journal submission. Use when: (1) Writing research papers, (2) Selecting target journals, (3) Formatting manuscripts, (4) Ensuring reporting guideline compliance, (5) Preparing submission materials.

Guided workflow for maintaining strategic redundancy between Serena memories and project documentation. Use after significant code changes, phase completions, or when new architectural patterns are discovered.

Design, visualize, and document database schemas with ERD generation, normalization guidance (1NF-BCNF), relationship mapping, and automated documentation. Create efficient database structures, generate SQL statements, produce interactive HTML docs, and maintain data dictionaries. Use for schema design, database modeling, ERD diagrams, normalization, and documentation generation.

Expert on your minimal zsh setup, dotfiles, and shell configurations. Use when asked about aliases, functions, shell scripts, zsh configuration, or dotfiles. ADHD-friendly explanations. Can fetch latest documentation using Context7 MCP.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Helix Personal AI Infrastructure for Sean Sylvia. CORE is the foundational skillthat loads at every session. Orchestrates specialized agents for health economicsresearch, grant writing, VBC modeling, and knowledge management. Spawns subagentsfor complex tasks and manages persistent memory, projects, and Obsidian vaultsynchronization.

Create, update, and maintain clear, accurate, and well-organized technical documentation for complex codebases. This agent focuses on understanding the current state of the code and existing documentation before proposing or making changes, ensuring documentation remains up to date, discoverable, and trustworthy for developers.

Garantiza lectura real, control de limites, registro en cache y validacion de citas/wikilinks en Obsidian.

Create and manage database schema migrations with reversible changes, clear naming, and safe deployment practices. Use this skill when writing database migration files, modifying database schemas, creating migration scripts, or managing database version control. When working on migration files in database migration directories, files defining schema changes (CREATE TABLE, ALTER TABLE, DROP TABLE), migration rollback/down methods, database index creation scripts, seed data or data migration files, ORM migration configurations (Prisma, Drizzle, TypeORM), or files handling database versioning and migration history.

Intelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步.

This skill should be used when the user asks to "create literate tests", "generate markdown tests", "specification-as-tests", "TDD with markdown", "agent-driven testing", or mentions test suites where markdown IS the test format. NOT for pytest/jest/unittest. Creates .md test files with inline assertions and uses a bundled custom test runner.

This skill should be used when analyzing a link to an AI tool and adding it to the awesome-ai-tools readme with proper categorization

Write or update documentation (tutorial, how-to, reference, explanation) with clear style, structure, visuals, API/ADR/runbook patterns. Use when: (1) Creating or updating docs after code changes, (2) During PR preparation or addressing review feedback, (3) Adding new features that need documentation, (4) Updating API endpoints, database schemas, or configuration, (5) Creating ADRs or runbooks, (6) Adding or updating diagrams and visual documentation, (7) When documentation needs to be written or revised, (8) For tutorial creation, how-to guides, or technical writing, or (9) For documentation standards compliance and structure. Triggers: write docs, update documentation, create documentation, write tutorial, document API, write ADR, create runbook, add documentation, document this, write how-to.

Validate that written content accurately reflects source materials.LOAD THIS SKILL WHEN: User says "驗證", "validate", "檢查準確性", "核對" | after writing notes/reports | ensuring content accuracy.CAPABILITIES: Source-target comparison, citation verification, fact checking, consistency check.

Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or discussing TS patterns. Emphasizes strict typing, composition, and modern tooling (bun/vite).

Auto-activating documentation cache with fresh API docs. Fetches and automatically consults cached documentation when user works with libraries/frameworks.

Write secure, optimized database queries using parameterized statements, proper indexing, and efficient data fetching patterns. Use this skill when writing database queries, ORM query methods, SQL statements, or data access layer code. When working on files containing Prisma queries, TypeORM query builders, raw SQL statements, database transaction logic, eager loading and joins, query optimization code, files implementing data pagination or filtering, cache strategies for expensive queries, or files handling database connection pooling and query timeouts.

Professional markdown writing standards for documentation and content creation