Claude Skills by sampleXbro

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

A relentless interview to sharpen a plan or design.

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Compact the current conversation into a handoff document for another agent to pick up.

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

Use when about to edit a file or run a state-changing command, or after any failure, correction, or surprising result.

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Use when writing, rewriting, or substantially updating the top-level README.md for AgentsMesh. Produces a concise, trustworthy, copy-paste-correct README — accurate header (banner + badges), a 60-second quickstart, real install/feature/links — without inventing APIs or duplicating LICENSE/CONTRIBUTING/CHANGELOG.

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Teach the user a new skill or concept, within this workspace.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

Use when an AI tool gains support for a feature agentsmesh does not yet expose — or exposes wrongly — and you must raise or correct an existing target's capability for project and/or global scope (rules, additionalRules, commands, agents, skills, mcp, hooks, ignore, permissions). Also use to audit every target for capability gaps, or to act on an audit/feature-request someone else wrote. Start by verifying the claim against the tool's OWN primary docs — such findings are frequently fabricated...

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Helps with advanced TypeScript work

Generate API endpoints

Generate REST API endpoints following project conventions

Debug failing builds and tests

Review the staged diff against the project working agreements.

Scaffold a new REST route with validation, handler, query and tests.

Review pull-request changes

Debugging

Generate REST API endpoints with validation and error handling

Debug failing tests and flaky behavior

Systematic debugging workflow

Generate REST API endpoints following project conventions

Review the working tree before opening a pull request.

Scaffolds a versioned REST route, its zod schema, and the matching test file.

Debug production failures and test regressions.

Scaffold new REST endpoints or controllers for existing resources

Systematic debugging workflow for production failures and test regressions.

Generate REST API endpoint scaffolding with validation and tests.

Systematic debugging workflow for Replit projects

Apply advanced TypeScript patterns including conditional types, template literal types, and mapped types

Generate REST API endpoints with validation and tests

Research docs and summarize decisions

Audit the whole repo for over-engineering, what can be deleted

Harvest ponytail: comments into a tracked debt ledger

Show ponytail's measured impact scoreboard (less code, cost, time)

Quick reference for ponytail levels, skills, and commands