All authors
Claude Skills by mikeparcewski
github.com/mikeparcewski152 skills0 installs61 views
- Plugin Json SchemaOfficial Claude Code plugin.json schema reference and validation guide. Use when creating or troubleshooting plugin.json manifest files. Covers all fields, auto-discovery behavior, path formats, and common validation errors.Votes: 0GitHub stars: 9
- Readme Style GuideCanonical README template and validation rules for Wicked Garden marketplace plugins. Use when: "write a README", "plugin README template", "README structure", "marketplace README", "README style guide", "validate README"Votes: 0GitHub stars: 9
- ReleasingRelease management and versioning toolkit for the wicked-garden plugin. Automates changelog generation, semantic versioning, and version bumping from git history. Use when preparing releases, generating changelogs, or managing plugin versions.Votes: 0GitHub stars: 9
- ScaffoldingComponent scaffolding toolkit for creating skills, context:fork worker skills, and hooks within the unified wicked-garden plugin. Generates complete, valid structures that pass validation out-of-the-box. Use when creating new domain components, setting up boilerplate, or ensuring proper structure from the start.Votes: 0GitHub stars: 9
- Skill{{description}} Use when {{use_when}}.Votes: 0GitHub stars: 9
- CrewVerify the crew:explain skill translates jargon-heavy gate findings and phase summaries into grade-8 plain languageVotes: 0GitHub stars: 9
- Agentic ArchitectFive-layer architecture validation, agent topology analysis, orchestration pattern assessment, and framework detection for agentic systems. Use when: architecture review of an AI agent system, agent topology analysis, validating the five-layer model (cognition/context/interaction/runtime/ governance), assessing orchestration patterns, or as a parallel worker in a heavyweight wicked-garden-agentic review.Votes: 0GitHub stars: 9
- Agentic Performance AnalystToken optimization, latency budgets, cost analysis, caching strategy, and parallelization assessment for agentic systems. Use when: performance optimization of an AI agent system, cost analysis or token-budget review, latency profiling, cache-strategy assessment, parallelization opportunities, or as a parallel worker in a heavyweight wicked-garden-agentic review.Votes: 0GitHub stars: 9
- Agentic Safety ReviewerGuardrails, prompt injection defense, PII protection, human-in-the-loop gates, and hallucination mitigation for agentic systems. Use when: safety review of an AI agent system, guardrail assessment, prompt injection audit, PII/compliance exposure check, HITL gate verification, or as a parallel worker in a heavyweight wicked-garden-agentic review. Cross-ref: EXECUTING injection/jailbreak/refusal-rate/drift probes against a live LLM feature with evidence artifacts + a ledger verdict is `wicked...Votes: 0GitHub stars: 9
- AgenticAgentic-systems domain skill: review, design, audit, and framework selection for AI agent systems. Routes to one of four actions (review | design | audit | frameworks) backed by the rubrics in refs/. Use when: "agentic review", "review this agent system", "full agentic codebase review", "trust and safety audit", "audit my agents for GDPR/HIPAA/SOC2/NIST compliance", "design an agentic system", "design a multi-agent architecture", "which agentic framework should I use", "compare LangChain vs ...Votes: 0GitHub stars: 9
- Agentic PatternsUse when designing or analyzing multi-agent architectures — covers core patterns (sequential, hierarchical, parallel, event-driven), anti-patterns, and the five-layer model (Cognition → Context → Interaction → Runtime → Governance) for separating concerns in production-grade agentic systems. NOT for reviewing existing agentic code (use review-methodology) or framework selection (use the frameworks skill).Votes: 0GitHub stars: 9
- Context EngineeringContext window management, token optimization, and memory patterns for efficient multi-agent systems. Use when: optimizing token usage in an agentic pipeline, designing memory scope for short / long-term / episodic state, or applying a context-loading strategy (anticipatory / JIT / hybrid).Votes: 0GitHub stars: 9
- FrameworksUse when selecting or comparing agentic frameworks (LangChain, LangGraph, CrewAI, AutoGen, etc.) — curated comparison by use case, language, and maturity. Gets latest context via Context7 when available. NOT for reviewing existing agentic code (use review-methodology) or architecture patterns (use agentic-patterns).Votes: 0GitHub stars: 9
- Review MethodologyUse when reviewing an agentic codebase for issues, risks, and maturity gaps — covers the four-phase review process (Detect → Analyze → Prioritize → Report) and the five-level maturity model (Prototype → Functional → Reliable → Production → Optimized) for assessing production readiness. NOT for architecture design (use agentic-patterns) or a live agentic review (the `wicked-garden-agentic` skill's `review` action).Votes: 0GitHub stars: 9
- Trust And SafetyTrust, safety, and control patterns for production agentic systems with human-in-the-loop gates and guardrails. Use when: designing guardrails or human-in-the-loop gates for an agent, or hardening an agentic system against prompt injection.Votes: 0GitHub stars: 9
- Archetypev11 work-shape archetype runner. When a prompt has been routed to one of the archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate, modernize), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or a direct per-archetype ask ...Votes: 0GitHub stars: 9
- Classifyv11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.Votes: 0GitHub stars: 9
- CoreCore utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "...Votes: 0GitHub stars: 9
- Data EngineerETL pipeline design, data quality assessment, schema validation, and performance optimization as a delegated worker skill. Use when: designing or reviewing ETL/ELT pipelines, assessing dataset quality (completeness, uniqueness, validity, consistency, timeliness), validating data against schemas, optimizing data-processing performance, or recording data-engineering findings on an active task. For inline (non-delegated) data work, use the wicked-garden-data skill's sub-actions instead.Votes: 0GitHub stars: 9
- DataData engineering, analysis, and ML toolkit. One skill, routed sub-actions: analyze (interactive EDA on a CSV/Excel/data file), profile / validate / quality (schema-level data engineering ops), ml review / ml pipeline (model review + training-pipeline design), pipeline design / pipeline review (ETL architecture), and ontology (recommend Schema.org, Dublin Core, DCAT, FOAF, GoodRelations, SKOS, or a custom shape for a dataset). Use when: "analyze this CSV/Excel/data file" / "explore this datas...Votes: 0GitHub stars: 9
- DeliberateCritical thinking framework applied before doing work. Challenges assumptions, reframes problems, identifies hidden opportunities, and validates whether the stated ask is the right ask. A way of approaching work, not a specialist discipline. Use when: challenging assumptions before implementation, reframing a stated problem, asking whether the right thing is being asked at all, "deliberate on this", "deliberate #42" (a GitHub issue number), "critically analyze this request before implementin...Votes: 0GitHub stars: 9
- DemoProduct demo domain: plan, record and review a polished demo video. plan — frames the audience, builds the story, picks hero cases and fresh alternates, runs a live rehearsal with measured timings, and writes a presenter script with a chapter list ready for recording. record — records each chapter as its own captioned, chaptered segment via Playwright + ffmpeg (DevTools screencast encoded live to H.264, no frame files on disk, final CRF 17), then stitches them into one MP4 with chapters. revi...Votes: 0GitHub stars: 9
- Domain CoverageCoverage evaluator + pre-build threat model for the domain-extraction workflow (CONTRACT-3 §2). Emits `coverage-report.json` from the estate store, then adversarially reviews the extracted domain model: hunts missing error paths, ungrounded rules, reason-less drops, cross-cluster smears, and coverage holes. Use when: dispatched as the `coverage` phase of a domain-extraction workflow run. The phase runs in a git worktree; WICKED_ESTATE_DB points at the live estate store. NOT for mining rules...Votes: 0GitHub stars: 9
- Domain ExtractorRule-extraction worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OW...Votes: 0GitHub stars: 9
- Domain ModelerDomain-graph worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into...Votes: 0GitHub stars: 9
- DomainThe FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME dom...Votes: 0GitHub stars: 9
- DraftThe quality floor for DOCUMENT deliverables drafted from a repo — brochures, one-pagers, flyers, pages, decks, memos — design guidance plus one self-check run before "done". Three floors: (1) READABLE — every text/background pair ≥ 4.5:1 (WCAG AA; 3:1 for large text) on COMPOSITED colours, print text ≥ 7pt; (2) SIZED TO THE BRIEF — the RENDERED page count honours the brief's page budget (wrappers are not pages); (3) GROUNDED — every number, URL and claim cites a repo path, mocks visibly label...Votes: 0GitHub stars: 9
- Editor ScaffoldBuild an artifact editor plugin for wicked-studio: scaffold a wicked-pack.json spec-2 pack with one self-contained HTML editor speaking wicked.editor/2 (its card, options and full-screen surfaces, Simple/Advanced) and /1 to older hosts, ask only for the permissions it needs, re-pin its hash, run the conformance cases in headless Chromium against studio's own plugin host, then install it into a wicked-crew daemon's editors. Use when: "build an editor plugin", "make a custom editor", "an edito...Votes: 0GitHub stars: 9
- Engineering Api DocumentarianSpecialize in API documentation — OpenAPI specs, endpoint documentation, request/response examples, error documentation, and authentication docs. Use when: API docs, OpenAPI specs, "document this API/endpoint", generating endpoint reference documentation from code, or when the engineering domain skill's `docs` action routes an api-type request here.Votes: 0GitHub stars: 9
- Engineering Migration EngineerSchema migrations, data backfills, deprecation paths, rollback plans, and the expand-contract pattern for changing live production systems without breaking them. Use when: schema migration, data backfill, splitting/merging tables or services, renaming fields or primary keys in production, changing data types or tightening constraints, sunsetting API versions, breaking changes to event payloads, or "how do we ship this breaking change safely?". NOT for large mechanical codebase changes with ...Votes: 0GitHub stars: 9
- Engineering Solution ArchitectDesign end-to-end solutions with appropriate patterns, technology choices, and architectural trade-offs — ADRs, system diagrams, cross-cutting concerns. Use when: system design, greenfield architecture, structural trade-offs, technology/pattern selection, "design the solution architecture", writing Architecture Decision Records, or when the engineering domain skill's `arch` action or the architecture knowledge module escalates genuinely structural design work.Votes: 0GitHub stars: 9
- EngineeringConsolidated engineering domain skill: senior-engineer code review, architecture analysis, systematic debugging, implementation planning, and documentation generation. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" / "evaluate component boundaries, coupling, or layer violations" (--scope module|service|system); "debug this error / bug / unexpected behavior" (hypothesis-driven root cause, reprodu...Votes: 0GitHub stars: 9
- ArchitectureComplete solution architecture design with patterns, decisions, and diagrams. Define overall system structure, technology choices, and architectural trade-offs. Use when: "design the architecture", "what's the overall structure", "architecture patterns", "technology stack", "system architecture"Votes: 0GitHub stars: 9
- BackendBackend engineering specialist for APIs, databases, server-side patterns, data modeling, scalability, and integrations. Use when: "design an API", "database schema", "how to handle auth", "backend performance", "REST endpoint", "query optimization", "server-side architecture"Votes: 0GitHub stars: 9
- DebuggingSystematic debugging and root cause analysis for investigating errors, diagnosing complex issues, and performance profiling. Use when: "debug this error", "why is this failing", "root cause analysis", "fix this bug", "investigate crash", "stack trace", "not working"Votes: 0GitHub stars: 9
- DocsUse when generating documentation from code, auditing documentation coverage for gaps, or detecting code-doc drift after a refactor. Covers generate (API docs, READMEs), audit (coverage metrics, undocumented exports), and sync (stale docs detection) in one skill. NOT for architecture documentation (use the architecture skill) or product requirements (use product/requirements-analysis).Votes: 0GitHub stars: 9
- FrontendFrontend engineering specialist for React, CSS, browser APIs, component design, accessibility, and performance. This skill should be used when the user asks about UI implementation, component review, or frontend-specific questions. Use when: "build a React component", "CSS layout issue", "frontend performance", "browser API", "component design", "accessibility check", "responsive design"Votes: 0GitHub stars: 9
- IntegrationDesign API contracts, service boundaries, and integration patterns. Define how components and services communicate and interoperate. Use when: "API design", "service integration", "how do these communicate", "API contract", "integration pattern", "REST API", "GraphQL", "event schema"Votes: 0GitHub stars: 9
- Large Scale MigrationHow to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/framework", "adopt a library across N files",...Votes: 0GitHub stars: 9
- PatchLanguage-agnostic code generation and change propagation. Use this skill when adding fields to entities, renaming symbols across files, or propagating changes that affect multiple files. Use when: "add field", "add a field to this entity", "rename everywhere", "rename this field across the codebase", "remove this field and all its usages", "propagate change", "generate migration", "update all references", "apply saved patches", "show what a change would affect" (patch-plan propagation preview...Votes: 0GitHub stars: 9
- System DesignUse when decomposing a system into components with clear boundaries, module organization, and interface contracts — the "how do we slice this?" question at design time. NOT for reviewing an existing system's health (use the architecture skill or engineering:arch).Votes: 0GitHub stars: 9
- Unit Test QualityLanguage- and framework-neutral guard against useless unit tests — the kind that pass forever, never catch regressions, and inflate coverage without protecting behavior. Provides two complementary thought-experiment filters (execution + behavior), a pre-write self-check, a taxonomy of seven recurring anti-patterns (tautological, assertion-free, implementation mirror, framework retest, constant verification, sleep-coupled, exception-swallowing), and a one-line decision rule per pattern. Use w...Votes: 0GitHub stars: 9
- Governed WorkerThe discipline every governed unit follows, by role — creator (fix/build), evaluator (reproduce/verify/judge) or neutral (triage/recon/plan): run the repo's checks in the worktree in the foreground and paste exit codes, prove any 'pre-existing' claim on the base, keep tool debris under the notes root, regenerate instead of hand-editing, check what the chosen stack already provides before writing code (evaluators flag duplicates of a built-in), evaluators write only to their output, neutral un...Votes: 0GitHub stars: 9
- GroundGrounding / assumption-check: pull deeper context from the knowledge layer (wicked-estate memory + knowledge) and the bus when uncertain, before acting. Use when: getting mixed signals from the codebase, about to commit to a non-obvious decision, prior decisions might exist for this exact problem, or you want to verify an assumption before action ("am I sure about this?", "have we decided this before?"). Returns relevant memories, knowledge chunks, recent bus events, and linked priors ranked ...Votes: 0GitHub stars: 9
- Jam Brainstorm FacilitatorRole-plays as focus group personas and synthesizes brainstorming discussions. Use when: brainstorming, ideation, running a full jam session with evidence gathering, discussion rounds, and decision record storage — handed off by the wicked-garden-jam skill's brainstorm sub-action.Votes: 0GitHub stars: 9
- Jam CouncilRuns structured multi-model council evaluations using external LLM CLIs. Use when: multi-model evaluation, council verdict on defined options, high-stakes decision needing genuinely independent model perspectives — handed off by the wicked-garden-jam skill's council sub-action.Votes: 0GitHub stars: 9
- JamOrchestrates AI-powered brainstorming sessions with dynamic focus groups. quick sessions are ephemeral (no storage). brainstorm and council sessions are tracked as native tasks (process) and stored via wicked-garden-mem (outcome). Use when: "brainstorm this", "explore ideas", "get different perspectives", "focus group", "what do you think about", "pros and cons", "quick check", "jam quick <idea>", "jam brainstorm <topic>", "jam council <topic> with options A/B/C", "multi-model evaluation", "c...Votes: 0GitHub stars: 9
- LearnLearn a topic or an event from outside sources and save it to the repository as KNOWLEDGE: research with cited sources, synthesize a claims ledger, walk the operator through it in chat, then author .wicked/knowledge/<slug>/ (topic.json, claims.jsonl, README.md) plus text-only skills that cite the claims. Every claim carries its source URL and observed_at. A refresh re-researches and proposes only changes: confirm, supersede, contradict, retire. Nothing is deleted silently. Use when: "learn a...Votes: 0GitHub stars: 9
- Mcp ScaffoldBuild a new MCP server that wicked-crew's broker can register and govern: scaffold a TypeScript server (fastmcp, OpenTelemetry, loglayer; the default) or a zero-dependency one-file stdio server (Node or Python), add tools with honest annotations, keep the one secret in the environment the broker injects, then probe it — initialize + tools/list, with each tool's class (read / write / destructive) derived exactly as the broker derives it. Use when: "build an MCP server", "scaffold an MCP serve...Votes: 0GitHub stars: 9
- McpUse an MCP tool from a governed wicked-crew unit, on any seat: list the tools your unit may try, then call one through the wicked-crew broker, which holds the server connections and secrets, judges every call by steering policy and records it. One command on every CLI; no MCP configuration. Use when: a task needs an external tool the operator registered in studio MCP tools ("look up the Jira issue", "query Sentry", "call the <server> tool"), "what MCP tools can I use", or a phase directive n...Votes: 0GitHub stars: 9