All authors
Claude Skills by mikeparcewski
github.com/mikeparcewski152 skills0 installs61 views
- Mem CaptureSession-teardown memory capture: sweep the conversation for durable learnings (decisions with a reason, patterns, gotchas, preferences), keep only what passes the durability test, classify each onto the estate kind/tier vocabulary, and batch-write them to wicked-estate memory; standing rules the user stated go to the review queue as policy proposals instead. Use when: dispatched by the wicked-garden-mem skill's capture action, at session end, before /clear or exit, or when the user says 'capt...Votes: 0GitHub stars: 9
- Mem IngestIngest source files into the wicked-estate knowledge store as cited chunks. Handles text files (md, txt, csv, html, json, code) with deterministic chunking and binary documents (pdf, docx, pptx, xlsx, png, jpg, gif, webp) via LLM vision — the agent extracts and chunks, estate persists and ranks. Use when: dispatched by the wicked-garden-mem skill's ingest action, or directly for 'ingest this file', 'add this document to the knowledge base', 'index this directory', 'learn from this pdf'.Votes: 0GitHub stars: 9
- MemCross-session memory + knowledge over wicked-estate. One skill, routed actions: store (a durable decision/pattern/gotcha), recall (the current project's memories; all scopes on opt-in), answer (cited synthesis from the knowledge + memory stores), review (browse coverage by kind/tier), forget (kind-guarded erase of a scope subtree), maintain (reflect + coverage pulse; estate consolidates in-store), ingest (file or directory → knowledge chunks, binary docs via LLM vision), and capture (session-...Votes: 0GitHub stars: 9
- PersonaOn-demand persona invocation system for applying named perspectives to any task. Sub-actions: `as <name> <task>` (invoke a persona), `list [--role R]` (discover personas), `define <name> --focus "..." [--save]` (create or update a custom persona). Use when: invoking a named persona ("as platform, review this auth flow"), applying a specific perspective or role lens to a task, listing available personas, defining a house persona that encodes a failure-mode defense, or reviewing work through a ...Votes: 0GitHub stars: 9
- Platform Compliance OfficerRegulatory compliance expert. Use when: SOC2, HIPAA, GDPR, PCI, regulatory compliance analysis of code and systems — identifies sensitive data handling, verifies required controls, detects violations, and provides prioritized remediation with evidence. NOT THIS WHEN: scenario-driven controls-evidence COLLECTION that must produce evidence artifacts + a ledger verdict row (a compliance test run) — use `wicked-garden-qe-compliance-test-engineer` (executor). THIS skill analyses and advises; it d...Votes: 0GitHub stars: 9
- Platform Privacy ExpertPrivacy and data protection specialist. Use when: PII, PHI, data protection, privacy by design, GDPR — detects personal data handling, classifies sensitivity, verifies privacy controls, and assesses data subject rights implementation.Votes: 0GitHub stars: 9
- Platform Security EngineerSecurity scanning and vulnerability assessment from DevSecOps perspective. Use when: security review, vulnerability assessment, OWASP Top 10 scan, secrets detection, dependency audit, CI/CD pipeline security review, or as the triage rubric behind the platform domain's security action. NOT THIS WHEN: a scenario-driven security TEST run that must produce evidence artifacts + a ledger verdict row (SAST/DAST/secrets scan as a QE gate input) — use `wicked-garden-qe-security-test-engineer` (execut...Votes: 0GitHub stars: 9
- PlatformPlatform domain skill: security scanning, incident triage, infrastructure review, and distributed-trace analysis. Routes to one of four inline actions (security | incident | infra | traces) backed by the rubrics in refs/, and links out to the domain's sub-skills (audit, compliance, health, observability, CI/CD tooling, peer-health) and workers. Use when: "security scan", "vulnerability assessment", "scan this PR for vulnerabilities", "run the security scanners", "incident", "production is do...Votes: 0GitHub stars: 9
- AuditAudit evidence collection and trail verification. Gathers artifacts, validates controls, generates audit reports, and maintains compliance documentation. Use when: "audit trail", "collect evidence", "audit report", "control testing", "compliance documentation", "gather audit evidence for SOC2/HIPAA/GDPR/PCI", or any former /wicked-garden:platform:audit invocation. NOT for defining compliance policies (use the compliance sub-skill) or ad hoc security checks (use the platform domain skill's se...Votes: 0GitHub stars: 9
- ComplianceUse when checking code or architecture against a regulatory framework (SOC2, HIPAA, GDPR, PCI) or translating a policy document into actionable controls — detects violations and provides prioritized remediation guidance. NOT for gathering audit evidence artifacts (use platform/audit). Use when: "is this compliant", "compliance check", "regulatory requirements", "check against SOC2/HIPAA/GDPR/PCI", or any former /wicked-garden:platform:compliance invocation.Votes: 0GitHub stars: 9
- ErrorsUse when investigating a production error spike or pattern across services — aggregates errors from discovered tracking sources, correlates with deployments, and assesses user impact. NOT for general observability (use platform/observability) or tracing latency (use the platform:traces command).Votes: 0GitHub stars: 9
- Gate Benchmark RebaselineRe-baseline procedure for the AC-11 gate-result benchmark lane (`tests/crew/test_gate_result_benchmark.py`). The benchmark enforces a 2× p95 SLO on `gate-result.json` ingestion. When a deliberate perf change lands on main (validator hardening, cache tuning, schema expansion), the baseline needs updating. Never re-baseline to silence a regression. Use when: "re-baseline AC-11 benchmark", "gate-result benchmark regression", "p95 benchmark baseline out of date", "update benchmark_baseline.json"...Votes: 0GitHub stars: 9
- Gh CliUse when you need gh CLI patterns beyond the basics — debugging failed workflow runs, bulk PR operations, release automation, or repo health checks. Provides composable gh invocations for power users. NOT for simple git commands (use Bash) or GitLab (use the glab-cli skill). Use when: "debug the failed workflow run", "bulk PR management", "release automation with gh", "gh operations", or any former /wicked-garden:platform:gh invocation (operations: workflows | prs | releases | repo).Votes: 0GitHub stars: 9
- Github ActionsWrite secure, optimized GitHub Actions workflows. Security-first approach with performance optimization. Use when: "GitHub Actions", "CI/CD pipeline", "workflow YAML", "deploy pipeline", "automate deployment", "debug workflow", "Actions security", "generate a workflow", "optimize this workflow", "troubleshoot the failing workflow", or any former /wicked-garden:platform:actions invocation.Votes: 0GitHub stars: 9
- Gitlab CiWrite secure, optimized GitLab CI/CD pipelines. Use when: "create CI/CD pipeline", "GitLab CI config", "fix pipeline", ".gitlab-ci.yml", "configure runners", "pipeline optimization"Votes: 0GitHub stars: 9
- Glab CliUse when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).Votes: 0GitHub stars: 9
- HealthSystem health overview from discovered observability sources. Aggregates errors, performance metrics, and SLO status across services. Correlates with deployments and code changes. Use for proactive health monitoring and post-deployment validation. Use when: checking aggregated system health, validating a post-deployment state, correlating production status with recent changes, "how is production", "check system health", or any former /wicked-garden:platform:health invocation. NOT for plugin-...Votes: 0GitHub stars: 9
- ObservabilityUse when monitoring or diagnosing the wicked-garden plugin ecosystem — health probes, contract assertions, hook traces, error pattern detection, and APM/logging/metrics toolchain discovery. NOT for distributed tracing across services (use the platform domain skill's traces action) or audit evidence (use platform/audit). Use when: "plugin health", "health probe", "hook didn't fire", "hook traces", "contract assertions", "validate script outputs", "what monitoring tools are installed", "toolch...Votes: 0GitHub stars: 9
- Peer HealthRun a health check on all wicked-* peer tools (wicked-vault, wicked-bus). Reports reachability, version vs. pin, and declared capability status for each peer. The replacement for `npx wicked-loom doctor` after Phase B absorption — peer-resolution now runs in-process via scripts/loom/, no external wicked-loom needed. Use when: "peer health", "check the wicked peers", "is wicked-vault reachable", "loom doctor", "peer version drift", "capability gap", or any former /wicked-garden:platform:peer-...Votes: 0GitHub stars: 9
- Prereq DoctorDiagnose missing tools and dependencies, offer to install them. Use when: "command not found", "ModuleNotFoundError", "missing tool", "install dependency", "prereq check", "setup validation"Votes: 0GitHub stars: 9
- Product A11y ExpertAudit accessibility compliance - WCAG guidelines, keyboard navigation, screen reader support, color contrast, semantic HTML. Use when: accessibility audit, WCAG compliance, keyboard-navigation review, screen-reader support check, or dispatched as the a11y lens of the product skill's ux-review --focus all. NOT THIS WHEN: axe-core/pa11y must actually RUN and produce evidence artifacts + a ledger verdict row (a scenario-driven a11y test run) — use `wicked-garden-qe-a11y-test-engineer` (executor...Votes: 0GitHub stars: 9
- Product Requirements AnalystElicit and document requirements with precision. Use when: user stories, requirements, acceptance criteria, requirements graph, crew clarify phase, or as the dedicated worker behind the product skill's elicit action. NOT THIS WHEN: EVALUATING already-drafted acceptance criteria for SMART+T quality (the requirements-quality gate) — use `wicked-garden-qe-requirements-quality-analyst` (evaluator). THIS skill elicits and documents requirements; it does not grade them.Votes: 0GitHub stars: 9
- Product Ui ReviewerVisual and UI design review. Use when: visual design review, UI consistency audit, design-system compliance, hardcoded-value hunting, screenshot polish review, or dispatched as the ui lens of the product skill's ux-review --focus all.Votes: 0GitHub stars: 9
- Product Ux DesignerDesign and evaluate user flows, interaction patterns, and information architecture. Use when: user flow design, IA mapping, Nielsen heuristic review, interaction-pattern selection, or dispatched as the flows+research lens of the product skill's ux-review --focus all.Votes: 0GitHub stars: 9
- Product Value StrategistValue-proposition design AND stakeholder alignment in one agent. Use when: value proposition, differentiation, JTBD mapping, defensibility, consensus building, or dispatched as the value lens of the product skill's strategy --focus all.Votes: 0GitHub stars: 9
- ProductProduct domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance", "define acceptance criteria", "stakeholder alignment", "build consensus", "analyze customer feedback", "elicit requirements", "write user stories", "aggregate customer feedback",...Votes: 0GitHub stars: 9
- Acceptance CriteriaDefine testable acceptance criteria from requirements and design. Bridge product requirements with QE test scenarios. Use when: "define acceptance criteria", "how do we know it's done", "what should QE test", "definition of done"Votes: 0GitHub stars: 9
- AccessibilityUse when auditing code for WCAG 2.1 AA compliance — keyboard navigation, ARIA patterns, color contrast, and semantic HTML. Produces prioritized remediation with code-level fixes. NOT for running automated a11y tools (use product:a11y command) or visual design review (use product/visual-review).Votes: 0GitHub stars: 9
- AnalyzeSentiment analysis, theme extraction, and trend detection from customer feedback. Use when: analyzing customer feedback for sentiment, extracting themes from support or survey data, or detecting trends in voice-of-customer signal.Votes: 0GitHub stars: 9
- ImageryVisual asset lifecycle management — analysis, generation, modification, and review. Three sub-skills cover the full creative pipeline with provider abstraction. Use when: generating, editing, analyzing, or reviewing an image — routes to the appropriate sub-skill (create / alter / review).Votes: 0GitHub stars: 9
- AlterAI-powered image modification: img2img editing and mask-based inpainting. Requires a provider that supports editing operations. Use when: "edit image", "modify image", "change image", "inpaint", "img2img"Votes: 0GitHub stars: 9
- CreateAI-powered image generation from text prompts using multiple providers. Supports 5 providers: cstudio, vertex-curl, OpenAI, Stability AI, Replicate. Use when: "generate image", "create image", "text to image", "new visual"Votes: 0GitHub stars: 9
- ReviewMulti-dimensional visual analysis and quality review of images. No external provider required — reads image files directly. Use when: reviewing an image for visual quality, brand-guideline adherence, or accessibility before production use.Votes: 0GitHub stars: 9
- ListenAggregate customer feedback from discovered sources across support, surveys, social, and direct channels. This skill should be used when the user needs to gather customer voice data to inform product decisions or understand sentiment. Use when: aggregating customer feedback from discovered sources, gathering voice-of-customer data, or surveying sentiment across channels.Votes: 0GitHub stars: 9
- MockupUse when you need a quick ASCII wireframe or HTML mockup in-chat without Figma overhead. NOT for production design work — use the figma plugin for that.Votes: 0GitHub stars: 9
- Requirements AnalysisUse when turning a vague idea or stakeholder ask into structured user stories with acceptance criteria and a requirements graph. For complexity >= 3 or compliance projects, defaults to graph mode. NOT for navigating an existing requirements graph (use requirements-navigate) or stakeholder alignment (use product:align).Votes: 0GitHub stars: 9
- Requirements GraphGraph-based requirements as atomic markdown files with rich frontmatter. Filesystem-as-graph: each AC is a node, directories are groupings, meta.md files are the human interface, frontmatter traces are the edges. Use when: defining requirements as a filesystem graph of atomic ACs, eliciting user stories, or laying out acceptance criteria with traceable edges.Votes: 0GitHub stars: 9
- Requirements MigrateConvert monolithic requirements documents into graph-structured requirements directories. Parses user stories and acceptance criteria from existing docs and creates atomic graph nodes. Use when: "migrate requirements", "convert to graph", "split requirements", "restructure requirements"Votes: 0GitHub stars: 9
- Requirements NavigateNavigate, query, and maintain requirements graphs. Regenerates meta.md on demand, checks coverage, finds gaps, and lints the graph structure. Use when: navigating or querying a requirements graph, generating a coverage report, refreshing meta.md, or linting graph structure for gaps.Votes: 0GitHub stars: 9
- ScreenshotScreenshot-based UI review using the seat's multimodal vision. Analyzes visual design from image files — layout, spacing, color, typography, responsiveness — and compares against design system rules. Use when: reviewing a UI screenshot for visual design, comparing rendered output against design system rules, or auditing layout from an image file.Votes: 0GitHub stars: 9
- StrategyStrategic business analysis for technical investments. Evaluates ROI, value proposition, competitive positioning, and market alignment. Provides decision support with business justification. Use when: building a business case for a technical investment, evaluating ROI or value proposition, or doing competitive positioning analysis.Votes: 0GitHub stars: 9
- SynthesizeGenerate actionable recommendations from customer voice insights. This skill should be used when the user needs to translate analyzed feedback into product priorities, feature recommendations, or strategic guidance. Use when: "recommendations from feedback", "translate feedback to priorities", "feature priorities from customer data", "synthesize feedback into action"Votes: 0GitHub stars: 9
- Ux ReviewUse when evaluating UX quality — user flows, information architecture, user research synthesis, personas, and usability assessment. Also covers generative UX flow design from requirements. NOT for visual design consistency (use visual-review) or accessibility code audits (use product/accessibility).Votes: 0GitHub stars: 9
- Visual DirectionFigure out what a section of content *should be* visually before reaching for any implementation pattern. Answers five structured questions — content structure, audience mental model, desired action, physical artifact metaphor, and the stupid-question test — then produces a one-paragraph visual brief for the implementer. Use when: designing a new section, evaluating a proposed visual treatment, or catching the nearest-neighbor trap (copying the adjacent project's pattern without asking if it...Votes: 0GitHub stars: 9
- Visual ReviewUse when auditing visual design for consistency — design system adherence, spacing tokens, typography scale, color palette, component patterns, and responsive polish. Structured checklist + scoring. NOT for UX flows or user research (use ux-review) or accessibility code audits (use product/accessibility).Votes: 0GitHub stars: 9
- ProveProve a claim by re-deriving it (run + gate) instead of asserting "done" — the one-line re-derivation verb — plus the compile action that emits a self-contained, vault-backed build gate into any repo. Use when: "prove it", "prove tests pass", "prove the build is clean", "re-derive done", "run the produces-gate", "gate this claim", "--with-attestations", "compile", "emit a build gate", "stamp a gate into a repo", "compile a repo-native build gate", "--trigger hook,ci", or any former /wicked-g...Votes: 0GitHub stars: 9
- Qe A11y Test EngineerAccessibility specialist — axe-core + pa11y, WCAG 2.1 AA / 2.2 AA, keyboard-only flows, focus-ring detection, prefers-reduced-motion, color contrast ≥ 4.5:1. Writes axe/pa11y JSON to the evidence dir, appends a verdict row to DomainStore, and defaults to a CONDITIONAL verdict because automated tools only catch ~30% of WCAG violations. Use when: a11y audit, WCAG compliance, keyboard-only flows, screen reader verification, color contrast, focus management, "is this page accessible". NOT THIS ...Votes: 0GitHub stars: 9
- Qe Acceptance Test ExecutorFollows structured qe test plans step-by-step, collecting evidence artifacts. Executes and captures only — does not judge or grade pass/fail. Writes evidence files to .wicked-qe/evidence/{run-id}/. Use when: acceptance test execution, evidence collection, test plan execution <example> Context: Test plan is ready and needs to be executed step by step. user: "Execute the acceptance test plan for the file upload feature." <commentary>Use acceptance-test-executor for mechanical step execution an...Votes: 0GitHub stars: 9
- Qe Acceptance Test ReviewerEvaluates evidence artifacts against test plan assertions independently. CRITICAL ISOLATION: Receives ONLY evidence file paths. Never sees execution context. Catches semantic bugs that self-grading misses. Use when: acceptance test review, evidence evaluation, test verdict <example> Context: Executor produced evidence and it needs independent evaluation. user: "Review the evidence from the file upload acceptance tests and render a verdict." <commentary>Use acceptance-test-reviewer for indepe...Votes: 0GitHub stars: 9
- Qe Acceptance Test WriterReads qe acceptance scenarios and produces structured, evidence-gated test plans. Transforms qualitative criteria into concrete, verifiable artifact requirements. Use when: acceptance testing, test plan generation, scenario verification design <example> Context: New feature scenario needs a structured test plan. user: "Write an acceptance test plan for the 'user can export data as CSV' scenario." <commentary>Use acceptance-test-writer to produce structured, evidence-gated test plans from sce...Votes: 0GitHub stars: 9