Art & Design

>- Interactively co-design and generate a high-density, semantic Tailwind-powered DESIGN_CONTEXT.md and zero-dependency live visual preview (design-preview.html). Supercharged with the OpenCode Data (opencode.ai/data) Technical Monospace telemetry engine, 6 distinct archetypes, strict 60-30-10 distribution, mathematical WCAG 2.1 AA/AAA verification, and native Tailwind CSS v4 Browser CDN (@tailwindcss/browser@4) architecture.

Test Web3 dApps end to end with Synpress (Playwright + MetaMask): wallet setup, connect, sign, send transactions, switch networks, and verify the result on-chain, not only in the UI. Use when a dApp, wallet flow, token transfer, staking, governance vote or smart-contract UI needs tests or a bug needs reproducing.

Research crypto project fundamentals through an evidence-backed 18-point framework covering product, team, security, tokenomics, unlocks, valuation and competitors. Use for project due diligence or focused fundamental research. Explain findings as Robin the Quant. Exclude portfolio crash tests, news triage, trade execution and price-only technical analysis.

Build a new multi-page WordPress-ready website in UiChemy from a business brief, choosing real section layouts from the UiChemy library and writing the copy. Use when the user asks to create, generate, draft or design a website, landing page or site for a business, client or idea.

Turn a design idea, mockup description, moodboard or brand brief into a WordPress-ready website in UiChemy, built to export to Elementor or Gutenberg. Use when the user asks to turn a design into a WordPress site, build a site that looks like a style or reference they describe, or go from design to Elementor or Gutenberg.

Pressure-test a proposed buy, sell or hold decision against its strongest opposing case, potential cognitive biases, missing assumptions and observable invalidation. Use for a trade gut check or investment decision critique. Explain as Robin the Quant. Exclude order execution and automatic portfolio sizing.

Add a blog to a UiChemy website project, with a listing page, article pages, archive pages and sample posts, then list or remove posts. Use when the user asks to add a blog, news or articles section, add or write blog posts, set up a blog page for a WordPress site, or delete a post.

Learn from a plan, a design, finished work or a plain topic — one plain-language question at a time, the user answers before seeing yours, each answer is tied to an idea from the classic software reliability books, and what was hard becomes Anki cards. `ready <PR>` checks the user can defend their own change before asking for review. Use when the user runs /learn on an issue, plan, PR, piece of code or topic, /learn ready on a PR they will ask a review for, or /learn review to go through due Anki cards.

Use when the user asks for an interactive or clickable HTML prototype, mockup, or walkthrough of a product UI flow, screen states, or a feature for reviewers (designers, product managers, developers) — "prototype", "clickable mockup", "show the screen states".

Write messages to people in the user's own voice, learnt from what they have written in chat (Slack, Teams, Google Chat), email and docs. Use it whenever the user asks you to reply to, respond to, answer, message, DM, email, ping or tell a person, team or channel, or to draft, send or schedule a chat message, thread reply, email or announcement that goes out under their name, and whenever they want text that should 'sound like me', 'in my voice' or 'how I'd say it'. Also use it to set up or refresh the voice profile: 'set up reply-like-me', 'learn how I write', 'study my Slack', 'scan my emails', 'update my voice'. Never use it for technical documents (RFCs, specs, ADRs, design docs, runbooks), pull requests, code review comments, commit messages, code or code comments, or for replies to the user themselves.

Review and simplify Python code design.

Review a diff, branch, PR, or existing code (a path or the whole repo) for code quality against ~/.claude/CODING_STANDARDS.md, using the deep-module vocabulary (module, interface, seam, adapter, depth, leverage, locality). Covers module depth and responsibility, state ownership and immutability, concept ownership and types (including making invalid states unrepresentable), dependency injection and config, error visibility, naming and function readability, and test quality; on a whole codebase it also questions the product's major design decisions against alternative directions. Use when the user says "quality review", "review for code quality", "review against my coding standards", "is this well designed", or invokes /quality-review. Not a bug hunt; use /code-review for correctness.

Use when a consequential decision or artifact (architecture plan, spec, risky diff, security design) deserves independent review by models from different families, and the user wants the models to debate directly instead of copy-pasting between chats.

>- Enforces a specification-first development workflow (SPEC.md gating protocol). Activates when designing or implementing complex multi-file features (3+ files), new API endpoints, database schema migrations, or cross-cutting architectural changes. DO NOT trigger for single-file edits, isolated bug fixes, test-only additions, or when an approved specification already exists.

Get instant 3D printing and CNC machining quotes and order custom parts from Make Parts Now (MakePartsNow.com), a US manufacturing service, straight from a CAD file in the project. Use when the user wants to 3D print, CNC machine, manufacture or prototype a part they designed (CadQuery, build123d, OpenSCAD, FreeCAD or any CAD tool), export a model for manufacturing, get a price or lead time, compare quantities, or order SLS PA12 nylon, TPU, FDM plastic, 6061 aluminum or C360 brass parts.

Use when a feature, refactor, or design is underspecified or has competing approaches — before writing code for work that touches data shape, security boundaries, public interfaces, or more than a few files. Not for typo-sized fixes.

>- Autonomous multi-specialist codebase audit and remediation framework. Activates when auditing, profiling, hardening, or systematically reviewing a repository or module for performance bottlenecks, security vulnerabilities, frontend/UI accessibility & rendering issues, or architectural technical debt using tiered subagents. DO NOT trigger for single-file bug fixes, greenfield feature creation, or trivial syntax questions.

>- Enforces SOLID principles (specifically Single Responsibility), Dependency Injection, Vertical Slice Architecture with Enterprise Integration Patterns (as architectural fallback), deterministic VSA boundary linting, portable repository-level GEMINI.md generation, real-time web research for optimal Big-O algorithmic complexity, high-performance & low-RAM open-source libraries with enterprise-safe licensing (MIT/Apache-2.0/BSD), deterministic static analysis for SRP & abstraction bypasses, framework-first conventions, parallel-ready test suites, CodeGraph/AST blast radius impact analysis, centralized secret injection via Infisical, AI-agent-ready tool design, and the Old Coder evidence-first TDD methodology. Activate whenever planning, exploring, refactoring, deploying, or writing code in any project.

Use when the user wants their own data out of a website they log into — order history, rides, bookings, transactions, watch or listening history, bills, statements, saved items — and there is no usable export, or an existing scraper repo is outdated, broken, or wants their password.

Get data from the internet into a project, for free where possible: find and call public APIs, or scrape public web pages when no API exists. Use when I ask to pull, fetch, collect, track or scrape data from a website or service (prices, weather, news, listings, stats, anything online), or to connect a project to an API.

Use when the user wants to know how another app, website or binary implements a feature without its source code ("how does Notion/Raycast/Linear do X", "reverse-engineer this behaviour", "look inside this app"), or mentions REA / rea-agents. Applies to any repo or project, including research done from inside one of the user's own repos.

Use this skill to triage the open PR queue before a release. Classifies every open PR into must-merge, candidate, superseded, or deferred; writes a working triage doc; and runs the merge loop end-to-end. Designed for the pre-release "PR speedrun" pass where a solo maintainer wants to clear the inbound backlog in a single session.

Measure email campaign outcomes and design useful tests with explicit cohorts, denominators, attribution limits, sample-size constraints, and decision rules. Use for campaign reports, A/B tests, holdouts, ROI questions, or claims that opens prove success.

Research and qualify potential business customers, produce evidence-backed account briefs and outreach drafts, and design reply handoff. Use for an AI SDR, prospect research, founder-led outbound, or sales introductions. Does not infer contact consent or autonomously buy lists or send email.