Craft

Plugin craft from marketplace apna-mart in Apna-Mart/claude-craft. Commands read from the repo's manifest — 9 days ago.

Skills (15)

• backend-best-practices

  Server-side quality baseline — load for any backend work in any stack: REST/gRPC/GraphQL endpoints, transactions, migrations, caching, queues and consumers, background jobs, webhooks, auth, service-to-service calls, service lifecycle. Owns the runtime and safety layer around the datastore: injection

• calculator

  Does math, unit and metric conversion, scientific calculation and currency conversion by running the `qalc` (Qalculate!) CLI instead of computing by hand. Use when the user asks to calculate, evaluate or simplify an expression; convert between units (length, mass, temperature, time, data, speed, are

• coding-best-practices

  Default code-quality baseline — load for writing, editing, refactoring, or reviewing code in any language or paradigm. Owns naming, SRP/DRY/KISS/YAGNI, guard clauses, error handling, edge cases, flag-free state (boolean flags → closed types, derived values, optional fields, state machines), immutabi

• dashboard-best-practices

  Designs, builds, reviews and fixes analytics and observability dashboards: purpose and audience, metric definitions, layout, chart per tile, filter wiring, default time range and grain, period comparisons, the incomplete-period trap, drill-down, and attributing success and failure to a cause (versio

• database-best-practices

  The database skill — load for any data, schema, index or QUERY work, and lead over backend-best-practices whenever the question is about the data or the SQL itself. Owns: which datasets exist, record grain and identity, keys, normalization vs deliberate duplication, constraints, history, tenancy, re

• design-patterns-best-practices

  Selects, compares and removes design patterns: the 22 GoF patterns plus functional (algebraic data types, Option/Result, lenses), concurrency (actor, CSP, backpressure) and distributed (saga, outbox, CQRS, circuit breaker) patterns; separates lookalikes (Strategy vs State vs Bridge, Adapter vs Proxy

• event-tracking-best-practices

  Designs and reviews product analytics event tracking by deciding where each event is sent from (client, backend, payment and app-store webhooks, CRM, jobs), what it carries (names, properties, ids, context) and how it is sent (identity, dedup ids, timestamps, delivery, consent), plus experiment expo

• explain-anything

  Explains any topic, technical or everyday, so it clicks: plain words a beginner can follow, one real-life analogy, one concrete example carried all the way through. Use when someone wants to understand a thing rather than get a fact: 'teach me X', 'explain X simply', 'help me understand X', 'ELI5',

• firebase-crash-fix

  Fixes Firebase Crashlytics crashes, non-fatals and ANRs on Android (Kotlin/Java), iOS (Swift/ObjC), Flutter (Dart) and React Native. Drives an evidence-first loop: pull the issue, its variants and sample events, de-obfuscate unreadable frames, read the code as shipped in the crashing release, trace

• github-bug-report

  Turns a bug report into a clear, complete, developer-ready GitHub issue. Use when someone wants to file, create, write, draft or open a bug for a backend service, frontend/web app, mobile app, or a multiplatform or multi-flavour project, even if they just paste a stack trace, a screenshot descriptio

• minimize-diff

  Opt-in only: load only when the user's latest message types /craft:minimize-diff or itself names minimize-diff (for example \"run minimize-diff on this branch\", \"use minimize-diff against main\"). Otherwise do not load it, even for a huge diff or a plain \"make this smaller\"; at most suggest /cra

• product-spec

  Interview-driven product spec builder — a PRD by any other name. Use WHENEVER the user wants to write, draft, create, update, scope, or structure a product spec, PRD, requirements doc, feature spec, or "one-pager" — even if they only describe an idea and say "help me spec this out", "I want to build

• render-performance-best-practices

  Frame-rate baseline for any frontend: hold 60–240 fps with no jank. Owns the frame budget, zero calculation in build/compose/body/render, collections in build (no per-frame filter/sort/find, no O(n²) row lookups), rebuild/recomposition/re-render scope, lazy and recycled lists (slivers, RecyclerView/

• testing-best-practices

  Load before fixing any bug in production code, so a failing test reproduces it first; and whenever writing, editing, fixing or reviewing tests (unit, integration, contract, e2e/UI, snapshot, screenshot, golden), including a red test someone wants green fast or a flaky test someone wants a sleep or r

• ui-state-best-practices

  Declarative frontend state baseline — UI=f(state), minimal facts, illegal states unrepresentable, single-owner hoisting, unidirectional data flow, which facts trigger a redraw, server-vs-client cache, state machines, effects-as-sync, race safety. Load before writing or reviewing any state-driven UI

Similar plugins