Browse Skills

6825 skills found

iterate-plan.md
1
1 export iterate-plan
2 mhylle from "mhylle/claude-skills-collection"
3 Update existing implementation plans through user feedback with thorough research and validation. This skill should be used when iterating on implementation plans, updating plans based on new requirements, refining technical approaches in existing plans, or when the user wants to modify a previously created plan file. Triggers on requests like "update the plan", "change the implementation approach", "iterate on this plan", or when feedback is provided about an existing plan document.
2026-01-05
code-style-enforcer.md
1
1 export code-style-enforcer
2 MaciWP from "MaciWP/CV_Astro"
3 Enforces code style standards including YOLO philosophy (minimal comments) and type hints. This skill should be used when writing Python code to ensure proper type hints, imports organization, naming conventions, and self-explanatory code without excessive comments.
2026-01-05
typo3-conformance.md
1
1 export typo3-conformance
2 netresearch from "netresearch/typo3-conformance-skill"
3 Evaluate TYPO3 extensions for conformance to official TYPO3 12/13 LTS standards, coding guidelines (PSR-12, TYPO3 CGL), and architecture patterns. Use when assessing extension quality, generating conformance reports, identifying technical debt, or planning modernization efforts. Evaluates: extension architecture, composer.json validation (mandatory fields, version constraints, deprecated properties), ext_emconf.php validation (state values, categories, constraints, critical TER restrictions), comprehensive ext_* files validation (ext_localconf.php, ext_tables.php, ext_tables.sql, ext_tables_static+adt.sql, ext_conf_template.txt), TYPO3 v13 deprecation detection (deprecated TypoScript files, addUserTSConfig, backend module migration, Site sets adoption), dependency injection, services configuration, testing coverage, Extbase patterns, best practices alignment, Crowdin integration, and GitHub workflow validation (issue templates, TER publishing automation). Supports PHP 8.1-8.4 and provides actionable improveme
2026-01-05
exploration-perspective-shift.md
1
1 export exploration-perspective-shift
2 synapseradio from "synapseradio/thinkies"
3 View situations from multiple vantage points to gain comprehensive understanding, useful for breaking out of fixed viewpoints, understanding stakeholder needs, or seeing problems differently. Triggered when: (1) asked to examine a situation through contrasting viewpoints or consider what different roles perceive, (2) When stuck on a problem with only one approach emerging, when making design decisions affecting multiple stakeholders, when resolving disagreements between stakeholders, when designing experiences bridging technical and user needs, during analysis paralysis with competing priorities, when evaluating stakeholder objections or concerns, when searching for solutions satisfying competing needs, when stakeholder feedback conflicts with technical constraints, before finalizing approaches impacting different user groups, or when tradeoffs between perspectives feel irreconcilable
2026-01-05
chapter-analyzer.md
1
1 export chapter-analyzer
2 AbdulSamad94 from "AbdulSamad94/Hackhaton-SpecsKitPlus"
3 Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
2026-01-05
test-driven-development.md
1
1 export test-driven-development
2 saw235 from "saw235/haskell-monorepo"
3 Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
2026-01-05
project-setup-wizard.md
1
1 export project-setup-wizard
2 MaciWP from "MaciWP/CV_Astro"
3 This skill should be used when analyzing an existing project to automatically generatepersonalized skills, agents, commands, and documentation based on detected patterns and needs.AUTO-ACTIVATES for: project setup, analyze project, setup claude code, personalize claude,auto-generate tools, detect project needs, bootstrap project.PROVIDES: Deep project analysis (code patterns, architecture, domain detection),automatic skill generation (personalized for THIS project's patterns),automatic agent generation (for recurring tasks), automatic command generation (for workflows),custom CLAUDE.md (with project-specific context and best practices).ANALYZES: Code patterns (repetitive endpoints, components, queries), project structure(architecture, layers, modules), dependencies (frameworks, libraries), recurring tasks(what developers do repeatedly), domain detection (invoicing, e-commerce, analytics, etc.).GENERATES: Personalized skills (e.g., "invoice-endpoint-builder" for invoicing project),task-specific
2026-01-05
requirements-feedback.md
1
1 export requirements-feedback
2 sjnims from "sjnims/requirements-expert"
3 This skill should be used when the user asks about "feedback loops", "iterate on requirements", "continuous documentation", "refine requirements", "update requirements", "requirements changed", "stakeholder review", "validate requirements", "incorporate feedback", "gather feedback", "requirements review meeting", "backlog refinement feedback", "user research findings", "sprint retrospective feedback", "help me gather feedback", "run a feedback session", "get input on my vision", "get input on my epics", "get input on my stories", "collect user feedback", "document feedback from meeting", "review requirements with stakeholders", or when they need guidance on collecting and incorporating feedback throughout the requirements lifecycle.
2026-01-05
best-practice-core.md
1
1 export best-practice-core
2 CANTAGESTUDIO from "CANTAGESTUDIO/CosmicAtlasPacker"
3 [Dev] Extracts and organizes best practices for a given topic into a minimal tree structure (max depth 3, max 5 children per node). Use during task planning when writing subtasks in Docs/{name}_Task.md - output is added under each subtask as a concise reference guide. Pure reasoning task with strict formatting rules: keywords/noun phrases only, no prose. (project)
2026-01-05
documentation.md
1
1 export documentation
2 Gaku52 from "Gaku52/claude-code-skills"
3 技術ドキュメント、README、API仕様書、アーキテクチャ図の作成方法。読みやすく、保守しやすく、チームに役立つドキュメント作成のベストプラクティス。
2026-01-05
backend-dev.md
1
1 export backend-dev
2 lpding888 from "lpding888/aiygw4.0"
3 后端开发专家,负责 Express.js + Knex.js + MySQL 8 + Redis 后端服务开发。遵循 OpenAPI 先行、TDD 推动、RBAC 安全、可观测性工程基线。处理 Provider 动态加载、缓存系统、数据库设计、内容管理 API 开发。适用于收到 Backend 部门任务卡(如 CMS-B-001)或修复类任务卡时使用。
2026-01-05
brainstorming-ideas-into-designs.md
1
1 export brainstorming-ideas-into-designs
2 houfu from "houfu/blog-alt-counsel"
3 Interactive idea refinement using Socratic method to develop fully-formed designs when partner describes any blog or newsletter idea, before writing a pitch or articles
2026-01-05
create-unit-test.md
1
1 export create-unit-test
2 tech-with-seth from "tech-with-seth/iridium"
3 Create Vitest unit tests following project patterns. Use when writing tests for functions, components, models, or route loaders/actions.
2026-01-05
questioning-hardcoded-values.md
1
1 export questioning-hardcoded-values
2 cassamajor from "cassamajor/xcnf"
3 Hardcoded strings and numbers need justification - they're either conventions that need documentation, magic numbers that should be constants, or assumptions that need verification
2026-01-05
docs-sources.md
1
1 export docs-sources
2 Consiliency from "Consiliency/treesitter-chunker"
3 Knowledge of documentation platforms and fetching strategies. Use when adding new documentation sources, determining fetch strategy for a docs site, detecting doc frameworks, or configuring the docs registry.
2026-01-05
ipv6-first.md
1
1 export ipv6-first
2 troykelly from "troykelly/claude-skills"
3 IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.
2026-01-05
comparative-matrix.md
1
1 export comparative-matrix
2 Dowwie from "Dowwie/agent_framework_study"
3 Generate structured comparisons and decision matrices across analyzed frameworks. Use when (1) comparing multiple frameworks or approaches side-by-side, (2) making architectural decisions between alternatives, (3) creating best-of-breed selection documentation, (4) synthesizing findings from multiple analysis skills into actionable decisions, or (5) producing recommendation reports for technical stakeholders.
2026-01-05
brutal-honesty-review.md
1
1 export brutal-honesty-review
2 pacphi from "pacphi/ampel"
3 Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.
2026-01-05
typescript-effect.md
1
1 export typescript-effect
2 bsamiee from "bsamiee/Parametric_Portal"
3 Enforces functional TypeScript patterns with Effect ecosystem. Use when (1) writing TypeScript functions or modules, (2) defining types or schemas, (3) handling errors or async operations, (4) structuring files with section separators, or (5) creating factories, dispatch tables, or Effect pipelines.
2026-01-05
repo-preflight.md
1
1 export repo-preflight
2 synapseradio from "synapseradio/thinkies"
3 Establish release readiness through layered validation that automatically repairs deterministic inconsistencies in versions, skill counts, and changelogs while surfacing issues requiring human judgment. Use when: (1) before creating any git commit in the thinkies repository, (2) after adding or modifying skills to catch metadata drift, (3) after version bumps to ensure consistency across all files, (4) skill counts in README files or version numbers in metadata files appear inconsistent, (5) as part of continuous integration validation, (6) after bulk operations that touched multiple skills
2026-01-05
narrative-diction.md
1
1 export narrative-diction
2 synapseradio from "synapseradio/thinkies"
3 Choose words for register, connotation, and precision. Use when: (1) asked to adjust formality or vocabulary, (2) text contains words like "delve" or "leverage", (3) writing for technical or general audience, (4) translating between casual and formal language, (5) text uses abstract terms without concrete reference.
2026-01-05
writing-email-for-jesse.md
1
1 export writing-email-for-jesse
2 obra from "obra/claude-pa"
3 Use when drafting emails on Jesse's behalf - captures his personal writing style, common phrases, and tone
2026-01-05
writing-unit-tests.md
1
1 export writing-unit-tests
2 samfolo from "samfolo/sigil"
3 Defines unit testing standards for the Sigil project. Applies when writing tests, reviewing test code, creating fixtures or mocks, or answering questions about testing conventions. Covers test structure, fixtures, mocks, assertions, table tests, and type safety in tests.
2026-01-05
tdd-red-phase.md
1
1 export tdd-red-phase
2 rubrical-studios from "rubrical-studios/gh-pmu"
3 Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures
2026-01-05