fpf-review
atholaArchitecture review using FPF (Functional Programming Framework) methodology. Evaluates codebases through functional, practical, and foundation perspectives. Use when conducting architecture reviews, evaluating system design. Do not use when simple code reviews, bug fixes, documentation updates.
project-execution
atholaExecute implementation plans with checkpoint validation, progress tracking, and quality gates. Use for task implementation, plan execution, progress tracking. Skip if no plan exists.
modular-skills
atholaArchitect skills as modular blocks to control token usage and complexity. Use when creating skills >150 lines, breaking down monolithic skills, or planning new architecture. Do not use for evaluating existing skills (use skills-eval) or writing human-facing prose (use writing-clearly-and-concisely). Check this skill before starting any new skill development.
rigorous-reasoning
atholaPrevents sycophantic reasoning through checklist-based analysis, categorical integrity, and evidence-following to uncomfortable conclusions. Red Flags: "I agree that", "You are right", "Great point", "Absolutely", "That is a fair point", "I can see why", agreement without validation, softening conclusions, hedging without evidence, retracting under pressure. Use when analyzing conflicts, evaluating ethical claims, or noticing sycophantic thought patterns. Do not use for routine implementation or simple factual questions. CRITICAL: This skill overrides conversational tendencies toward politeness. Agreement requires validity and accuracy.
smart-sourcing
atholabalancing accuracy with token efficiency.
makefile-generation
atholaGenerate language-specific Makefiles with testing, linting, and automation targets. Use for project initialization and workflow standardization. Skip if Makefile exists.
bloat-detector
atholaDetect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Use when context usage high, quarterly maintenance, pre-release cleanup, before refactoring. Do not use when active feature development, time-sensitive bugs, codebase < 1000 lines.
style-learner
atholaLearn and extract writing style patterns from exemplar text for consistent application. Use when creating a style guide from existing content, ensuring consistency across documents, learning a specific author's voice, customizing AI output style. Do not use when detecting AI slop - use slop-detector instead. just need to clean up existing content - use doc-generator with --remediate. Use this skill to build style profiles from exemplar text.
skill-authoring
atholaGuide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.
workflow-monitor
atholaautomatically create GitHub issues for workflow improvements via /fix-workflow. Use when workflows fail, timeout, or show inefficient patterns. Do not use when normal workflow execution, simple command errors.
project-specification
atholaTransform project briefs into testable specifications with acceptance criteria. Use for requirements translation, spec creation, pre-implementation. Skip if spec exists or still exploring.
code-quality-principles
atholaProvides guidance on fundamental software design principles to reduce complexity, prevent over-engineering, and improve maintainability.
review-chamber
atholaCapture and retrieve PR review knowledge in project memory palaces.
proof-of-work
atholaEnforces "prove before claim" discipline - validation, testing, and evidence requirements before declaring work complete. Use when claiming work is complete, recommending solutions, or finishing implementations, improvement validated, workflow optimized, performance improved, or issue resolved. Do not use when asking questions or for work clearly in-progress. MANDATORY: This skill is required before any completion claim.
response-compression
atholahype, and unnecessary framing. Includes termination and directness guidelines.
doc-generator
atholaGenerate or remediate documentation with human-quality writing and style adherence. Use when creating new documentation, rewriting AI-generated content, or applying style profiles. Do not use for slop detection only (use slop-detector) or learning styles (use style-learner).
decisive-action
atholaGuidance on when to ask clarifying questions vs proceed with standard approaches. Reduces interaction rounds while preventing wrong assumptions.
gemini-delegation
atholaGemini CLI delegation workflow implementing delegation-core for Google's Gemini models. Use when delegation-core selected Gemini, need Gemini's 1M+ token context window, batch processing required. Do not use when deciding which model to use (use delegation-core first), gemini CLI not installed.
clear-context
atholaAutomatic context management with graceful handoff to continuation subagent. Use when Context usage approaches 80% during long-running tasks. This skill enables automatic continuation without manual /clear. The key insight: Subagents have fresh context windows. By delegating remaining work to a continuation subagent, we achieve effective "auto-clear" without stopping the workflow.
war-room
atholaMulti-LLM deliberation for strategic decisions via expert pressure-testing and consensus building. Use for critical, irreversible, or high-stakes architecture choices and conflicts. Skip for trivial or reversible decisions.
subagent-testing
atholaTDD-style testing methodology for skills using fresh subagent instances to prevent priming bias and validate skill effectiveness. Use when validating skill improvements, testing skill effectiveness, preventing priming bias, measuring skill impact on behavior. Do not use when implementing skills (use skill-authoring instead), creating hooks (use hook-authoring instead).
development-workflow
atholadetailed development workflow with modular patterns for git, code review, testing, documentation, and deployment
workflow-setup
atholaConfigure GitHub Actions CI/CD workflows for automated testing, linting, and deployment. Use for CI/CD setup and quality automation. Skip if CI/CD configured or using different platform.
delegation-core
atholaDelegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling. Use when tasks exceed context window or need cheaper processing. Do not use when task requires reasoning by Claude.
shell-review
atholaAudit shell scripts for correctness, portability, and common pitfalls. Use when reviewing shell scripts, CI scripts, hook scripts, wrapper scripts. Do not use when creating new scripts - use attune:workflow-setup.
optimizing-large-skills
atholaSystematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Use when skills exceed 300 lines, multiple code blocks (10+) with similar functionality, heavy Python inline with markdown, functions >20 lines embedded. Do not use when skill is under 300 lines and well-organized. creating new skills - use modular-skills instead. Consult this skill when skills-eval shows "Large skill file" warnings.
skills-eval
atholaEvaluate and improve Claude skill quality through auditing. Use when reviewing skill quality, preparing skills for production, or auditing existing skills. Do not use when creating new skills (use modular-skills) or writing prose (use writing-clearly-and-concisely). Use this skill before shipping any skill to production.
code-refinement
atholaAnalyze and improve living code quality: duplication, algorithmic efficiency, clean code principles, architectural fit, anti-slop patterns, and error handling robustness. Use when improving code quality, reducing AI slop, refactoring for clarity, optimizing algorithms, applying clean code principles. Do not use when removing dead/unused code (use conserve:bloat-detector). reviewing for bugs (use pensive:bug-review). selecting architecture paradigms (use archetypes skills). This skill actively improves living code, complementing bloat detection (dead code removal) with quality refinement (living code improvement).
precommit-setup
atholaConfigure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured.
project-planning
atholaTransform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.
slop-detector
atholaDetect and flag AI-generated content markers in documentation and prose. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).
safety-critical-patterns
atholaGuidelines from the NASA Power of 10 rules for writing robust, verifiable code. Adapted for general software development with context-appropriate rigor. Use when writing critical code paths, reviewing for robustness, improving code quality. Do not use as rigid requirements for all code - match rigor to consequence.
methodology-curator
atholaSurfaces expert frameworks and proven methodologies before creating OR evaluating skills, hooks, agents, or commands. Helps select approaches from domain masters. Use when starting creation workflows, evaluating methodology gaps, or seeking domain expertise. Do not use if you already have a specific methodology or are fixing syntax/structural issues.
war-room-checkpoint
atholaInline reversibility assessment for embedded War Room escalation from commands. Use at decision points to determine escalation need. Skip for standalone strategic decisions.
architecture-paradigms
atholaInteractive selector and router for architecture paradigms. Use when selecting architecture patterns for new systems, comparing paradigm trade-offs, creating architecture decision records, evaluating architecture fit for team size and domain complexity, planning implementation roadmaps. Do not use when implementing a specific known paradigm - use the specific architecture-paradigm-* skill (hexagonal, layered, microservices, etc.) instead. reviewing existing architecture - use architecture-review instead. Use this skill BEFORE making architecture decisions. Check even if unsure about needs.
session-management
atholaManage Claude Code sessions with naming, checkpointing, and resume strategies. Use when organizing long-running work, creating debug checkpoints, managing PR reviews.
qwen-delegation
atholaQwen CLI delegation workflow implementing delegation-core for Alibaba's Qwen models. Use when delegation-core selected Qwen, need Qwen's large context capabilities, batch processing required. Do not use when deciding which model to use (use delegation-core first), qwen CLI not installed.
project-brainstorming
atholaGuide project ideation through Socratic questioning and constraint analysis for actionable project briefs. Use for starting projects, exploring problems, comparing approaches, feasibility. Skip if requirements are clear.
debug-helper
atholaSystematic debugging approach for identifying and fixing issues
test-writer
atholaWrite comprehensive tests following TDD and BDD principles
api-designer
atholaDesign RESTful APIs with best practices for consistency and usability
git-workflow
atholaGit best practices for version control and collaboration
coding-assistant
atholaProvides coding assistance with best practices and code review