dcramer
- 28 skills
- 0 followers
- 10 hours ago last updated
- ▌ Testing Guidelines · dcramerGuide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
- ▌ Icons QA · dcramer bundleRuns visual and structural QA for this repository's Stream Deck icons. Use after icon or build changes, or when asked to inspect, review, dogfood, or visually validate icon assets, paired states, the 5 x 3 preview, browser rendering, responsive behavior, or icon accessibility.
- ▌ Odie · dcramer bundleUse when transcript, commit, Sentry, GitHub, CI, review, or Garfield history suggests recurring failure patterns that might become hard deterministic checks. Analyze the evidence, reject judgment-based ideas, and output only mechanically enforceable lint, schema, CI, workflow, or deterministic test rules. Do not use for general code review, broad tool selection, or implementation unless explicitly asked.
- ▌ Design · dcramer bundleDesigns, prototypes, reviews, and polishes intentional, accessible visual artifacts with HTML, CSS, SVG, and JavaScript. Use for UI design, design systems, wireframes, HTML decks, interactive prototypes, visual variations, accessibility audits, and design-quality reviews.
- ▌ Garfield · dcramer bundleCoordinates bounded subagent review, intent-preserving fixes, and validation after a meaningful implementation slice; use only when the user explicitly asks to run Garfield or its review-fix-verify loop before handoff, not for standalone reviews, CI iteration, brainstorming, or skill authoring.
- ▌ Testing Agents · dcramer bundleDesigns and reviews tests for agents and LLM-backed workflows. Use when coverage involves model behavior, tool choice, semantic output, flaky evals, mocked agent paths, brittle assertions, or fixture overfitting; do not use for ordinary deterministic tests or general prompt experiments.
- ▌
- ▌
- ▌ Debug Self · dcramerDebug yourself or other Ash sessions by analyzing logs, history, and source code
- ▌ Architecture Review · dcramerUse when reviewing codebase health, finding structural issues, or auditing architecture quality before major changes
- ▌
- ▌ Todo · dcramerAdd, complete, list, edit, or delete todo items. Use whenever the user mentions tasks being done, asks what's left, wants to add/remove tasks, or references their todo list.
- ▌ Google · dcramer bundleManage Gmail and Google Calendar with capability-backed auth and operations. Use when asked to check inbox, summarize emails, give a day at a glance, send an email, review calendar events, or schedule meetings.
- ▌ Schedule · dcramerCreate, list, update, or cancel scheduled tasks and reminders. Use whenever the user asks to be reminded, wants something to happen at a specific time, sets up recurring checks, or asks about upcoming scheduled items.
- ▌ Deslop · dcramer bundleSimplifies existing Peated code, docs, prompts, plans, or explanations without changing required behavior. Use when asked to deslop, simplify, remove jargon, trim, or reduce overengineering. Do not use for unrelated feature work or broad cleanup.
- ▌ Peated QA · dcramer bundleUse when manually QAing Peated changes across the API, CLI, or web UI; selecting smoke checks after code changes; using agent-browser for Peated flows; verifying local behavior beyond tests and lint.
- ▌ Peated CLI · dcramer bundleUse Peated's authenticated API client for OAuth-backed production API reads and writes through `pnpm cli auth` and `pnpm cli api`. Direct database-backed CLI command groups are legacy and unsupported for operations.
- ▌ Peated Catalog · dcramer bundleCatalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set. Use for missing Bottles, wrong facts, Series membership, images, aliases, references, or duplicate review. Do not use for code changes or store-price queue moderation.
- ▌ Peated Writing · dcramerWrites and reviews user-facing Peated copy in the product's voice. Use for interface labels, empty states, errors, help text, announcements, marketing, rewrites, and Peated voice or copy reviews. Do not use for code comments or technical documentation that does not speak to customers.
- ▌ Agent Design Review · dcramer bundleDesigns, reviews, and iterates on LLM agents and agent-like workflows. Use when asked to "design an agent", "review this agent", "improve our system prompt", "optimize prompts for caching", "improve tool calling", "reduce hallucinated tool calls", "add structured outputs", "decide if this should be multi-agent", "reduce false positives", "tune agent thresholds", or "build evals for this agent". Covers architecture choice, cache-friendly prompt templates, tool and schema design, runtime loops, trust boundaries, and eval-driven iteration.
- ▌ Peated Scraper Queue · dcramer bundleModerates Peated retailer listings in the store-price match queue. Use for requests to review or clear the scraper queue, approve Bottle matches, create Bottles from proposals, apply proposed corrections, retry failed classification, or ignore unsupported listings. Do not use for scraper setup, runs, or debugging.
- ▌ Openspec Explore · dcramerEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
- ▌ Openspec Propose · dcramerPropose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
- ▌ Openspec Sync Specs · dcramerSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
- ▌ Openspec Apply Change · dcramerImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- ▌ Openspec Archive Change · dcramerArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
- ▌ Dex · dcramer bundleManage tasks via dex CLI. Use when breaking down complex work, tracking implementation items, or persisting context across sessions.
- ▌ Dex Plan · dcramerCreate dex task from markdown planning documents (plans, specs, design docs, roadmaps)