Search Results for "document"
explore-docs
Retrieve authoritative library documentation and code examples.
api-patterns
REST/GraphQL/tRPC API pattern library with validation, error handling, and documentation. Use when creating backend APIs.
architecture-patterns
Architecture design templates, mermaid diagrams, documentation patterns, and validation tools. Use when designing system architecture, creating architecture documentation, generating mermaid diagrams, documenting component relationships, designing data flows, planning deployments, creating API architectures, or when user mentions architecture diagrams, system design, mermaid, architecture documentation, or component design.
decision-tracking
Architecture Decision Records (ADR) templates, sequential numbering, decision documentation patterns, and decision history management. Use when creating ADRs, documenting architectural decisions, tracking decision rationale, managing decision lifecycle, superseding decisions, searching decision history, or when user mentions ADR, architecture decision, decision record, decision tracking, or decision documentation.
doc-sync
Documentation synchronization using Mem0 for tracking relationships between specs, architecture, ADRs, and roadmap
spec-management
Templates, scripts, and examples for managing feature specifications in specs/ directory. Use when creating feature specs, listing specifications, validating spec completeness, updating spec status, searching spec content, organizing project requirements, tracking feature development, managing technical documentation, or when user mentions spec management, feature specifications, requirements docs, spec validation, or specification organization.
grounded-answer
Provide accurate, evidence-based answers by referencing sources from documents, textbooks, or research papers. Use when user asks for factual or source-backed responses.
global-commenting
Write self-documenting code with minimal, helpful comments that explain large sections of logic without cluttering the codebase. Use this skill when writing code comments, documenting complex logic, reviewing whether comments are needed, writing function documentation, explaining non-obvious code sections, ensuring code clarity through naming and structure, avoiding temporary or change-related comments, keeping comments evergreen and future-relevant, or deciding between adding comments versus refactoring for clarity. Apply this skill when writing or reviewing any code file to ensure comments add value without creating noise, and that code is primarily self-explanatory through clear naming and structure.
global-conventions
Follow project-wide development conventions for file organization, version control, documentation, and dependency management. Use this skill when organizing project directories and files, writing README documentation, creating commit messages, working with git branches, managing pull requests, configuring environment variables, handling secrets and API keys, managing project dependencies, setting up feature flags, maintaining changelogs, defining testing requirements, establishing code review processes, or structuring the overall project architecture. Apply this skill when setting up new projects, refactoring project structure, working with version control, managing configuration files, or ensuring the project follows consistent organizational patterns and best practices.
global-tech-stack
Reference and maintain documentation of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when choosing technologies for implementation, adding new dependencies or libraries, setting up project infrastructure, configuring build tools and package managers, integrating third-party services (authentication, email, monitoring), selecting appropriate frameworks for features, ensuring consistency with existing technology choices, documenting technology decisions, reviewing technology compatibility, or onboarding team members to the tech stack. Apply this skill when making technology decisions, adding new tools or services, documenting the stack, or ensuring new code aligns with the project's established technical architecture.
obsidian-plan-wiki
This skill should be used when creating or working with modular project plans stored as Obsidian-compatible markdown wikis. Use when the user asks to create a plan, roadmap, or documentation system that needs to be navigable in Obsidian, or when working with existing plan wikis that use the %% [ ] %% task tracking format.
the-archivist
This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.
update-docs
Update all documentation in .plans, CLAUDE.md files, docs, and .tasks to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
career-advisor
Career Advisor agent for PhD application planning and career management. Helps with university research, application tracking, professor matching, and career documentation.
react-components
Build production-ready React components with TypeScript. Use when creating UI components (buttons, inputs, modals, cards), implementing hooks patterns, component composition, or setting up component documentation/testing. Covers accessibility, error boundaries, and performance optimization.
rest-api-design
RESTful API design and OpenAPI specification generation. Use when: (1) Designing new REST API endpoints, (2) Creating OpenAPI/Swagger specifications, (3) Choosing HTTP methods, status codes, or URL patterns, (4) Implementing pagination, filtering, or sorting, (5) Planning API versioning strategy, (6) Reviewing API design for best practices, (7) Generating API documentation templates.
today
Get today's date for web searches and date-sensitive tasks. Auto-invoke before any WebSearch that includes a year (e.g., "React 2024", "Python 2025"), when searching for current documentation, latest releases, or recent information. Ensures searches use the correct current year instead of outdated dates.
Frequently Asked Questions
What is a Claude Skill?
It is a modular, protocol-based instruction set that enables Claude to perform specific tasks autonomously and efficiently.
How is this different from regular prompts?
Skills use the official Anthropic protocol for better token efficiency and automatic triggering compared to static prompts.
Does it support the new Claude Code CLI?
Yes, we provide specialized one-click installation commands designed specifically for Claude Code and OpenCode.
Can I use these skills in Cursor?
Absolutely, our library is fully compatible with popular IDEs and extensions including Cursor, Codex, and AntiGravity.
Are the skills on the website free to use?
Most skills in our 90,000+ database are free and open-source for the community to download and deploy.
How can I contribute my own skills?
Developers can easily share their work by submitting their own skill repositories through our community portal.