Apply documentation standards: comment why not what, minimal comments (prefer clear code), maintain README with quick start, update docs with breaking changes. Use when writing comments, creating docs, reviewing documentation, or discussing what to document.
Guide for writing clear, comprehensive technical documentation including README files, API docs, guides, and inline documentation
Fetch the README content from a GitHub repository. Use when the user asks for a repository README, documentation, or wants to read the repo's main documentation file.
General Go development guide. Use when writing Go code, implementing best practices, formatting code, writing tests, using mocks, handling errors, or understanding Go coding conventions. Covers code style, testing patterns, dependency injection, interface design, and performance optimization. Project-agnostic guidelines applicable to any Go codebase.
Creating documentation from legacy code when none exists, focusing on what future maintainers need to know
Creates concise, behavior-focused documentation for humans and AI. Use after feature implementation OR bug fixes to document HOW THE PRODUCT BEHAVES. NOT a changelog - documents current behavior, not change history.
Creates comprehensive implementation guides for individual steps from implementation plans, breaking down complex steps into granular tasks with clear acceptance criteria and developer context
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
Generate a quick compliance checklist from the Four Learning Design Pillars. Use when users want a practical checklist for reviewing content, a quick audit tool, or verification questions for specific pillars.
Knowledge and patterns for understanding project structures, architectures, and codebases.
Collaboratively create and refine new skills through iterative design - validate needs, design structure, draft content, test, and refine.
Master emerging technologies including blockchain, cybersecurity, QA testing, and specialized tech roles. Stay ahead with cutting-edge technologies.
Analyze and categorize installed Nixtla Skills for forecasting guidance. Use when seeing available skills or selecting the right one. Trigger with 'list nixtla skills' or 'what skills'.
Create detailed implementation plans for software features and refactoring tasks. Use this skill when planning new features, architectural changes, or major refactoring efforts.
Collaborative strategic thinking for founders, operators, and decision-makers. Use when someone needs help working through business strategy, product direction, positioning, prioritization, or major decisions. Triggers include requests to think through strategy, evaluate tradeoffs, pressure-test ideas, clarify direction, scope products, or navigate pivots. Not for execution, for clarification and decision-making.
Aggregate flat building elements into hierarchical construction documents with 4-level cost breakdown structure.
