emtcmca
- 14 skills
- 0 followers
- 10 hours ago last updated
- ▌ Orchestration · emtcmcaThe promptsmith Layer 2 coordinator. Use for a multi-domain request that spans more than one specialist — it sharpens the query, decomposes it into non-overlapping slices, routes each to the right gallery agent (dispatched as a subagent), logs any slice no agent covers, resolves cross-agent conflicts, and synthesizes one coherent deliverable. Invoked by /orchestrate. Requires a host that can spawn subagents (Claude Code) — this is the power layer, not the paste-anywhere core.
- ▌ Planner · emtcmcaTurn a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs breaking down and sequencing before implementation starts.
- ▌ Debugger · emtcmcaTurn a stack trace, exception, failing test, or bug report into ranked root-cause hypotheses plus the cheapest observation that confirms or kills each one. Use when something is broken, a test started failing, or a regression appeared and the cause is not yet known.
- ▌ Evaluator · emtcmcaGrade an artifact against named criteria and return a scored verdict plus the highest-leverage fixes, deriving a rubric if none is supplied. Use to score and iterate on a prompt, doc, plan, spec, UI, or piece of copy.
- ▌ Docs Writer · emtcmcaDocument code, a feature, or an API so the next person can use it without asking — README, usage guide, or architecture decision record. Use when writing or improving developer-facing documentation.
- ▌ Test Author · emtcmcaWrite focused tests that prove behavior through the public interface, naming what each test proves. Use when adding test coverage, writing unit or integration tests, or locking in a bug fix with a regression test.
- ▌ API Reviewer · emtcmcaReview an existing HTTP endpoint or API contract for correctness, contract clarity, and abuse potential. Use when a REST or GraphQL surface needs review before it ships.
- ▌ Data Modeler · emtcmcaTurn requirements into a sound database schema plus a safe migration path. Use when designing tables, columns, relationships, indexes, and constraints, or when planning a schema change or migration in Postgres, MySQL, or SQLite.
- ▌ Feature Spec · emtcmcaTurn a rough feature idea into a tight, buildable specification with scope, acceptance criteria, and an explicit cut line. Use when an idea, ticket, or request needs to become something a team can actually build.
- ▌ Backend Builder · emtcmcaBuild an endpoint or backend service to a stated contract — input-validated, authorized, and idempotent. Use when implementing server-side functionality, API routes, or business logic rather than reviewing it.
- ▌ Security Review · emtcmcaReview a change for how it gets attacked, abused, or leaked, ranked by real-world impact rather than checklist severity. Use when code touches authentication, authorization, untrusted input, secrets, payments, file uploads, or personal data.
- ▌ Frontend Builder · emtcmcaBuild UI components that are usable, accessible, and on-brand, covering loading, empty, and error states. Use when implementing user-facing interface work in React or any component framework.
- ▌ Refactor Planner · emtcmcaTurn messy code plus a goal into a safe, staged refactor plan where every step leaves the build green. Use when restructuring, untangling, or cleaning up existing code without changing its behavior.
- ▌ Prompt Engineering · emtcmca bundleSharpen a vague request into a complete prompt, author a reusable agent or system prompt, or review a draft prompt through expert lenses. Use when a prompt is under-specified, when writing a system prompt for an agent, or when prompt output quality is inconsistent and you need gap-filling and a professional review pass.