House style for generated HTML documents. Use whenever the user asks to generate, write, or update an HTML document (guides, architecture docs, requests, reports, walkthroughs). Applies the warm-paper palette and panel/callout/TOC structure from the Loop architecture doc, in a compact form with ui-sans-serif as the default font.
Architecture playbook for LLM-powered data assistants over secured SQL (distilled from secure reference patterns). Use when designing, building, reviewing, or debugging any feature where an LLM authors SQL, reads firm data, or streams rich answers — tool loops, row-level security, sensitive-data masking, data-reference hydration, output guarding, audit — and for Blazor Server app design around streaming LLM UIs (service scoping, circuits, SignalR, JS interop). Also applies when porting these patterns to a new app.
Methodical feedback-loop harness — turn a goal into a Reason→Act→Observe→Check loop with a checkable done-criteria, real verification, a hard iteration cap, memory between passes, and a logged trail. Use when a task needs iteration to reach quality rather than a one-shot answer ("loop on this until…", "keep iterating until X", "run a goal loop", "set up a feedback loop", overnight/unattended goal runs, "build me X and make it actually good"). Invoke with /loop-mode <goal>. Composes with the built-in /loop, which supplies the cadence/trigger; this skill supplies the action and the stop-condition.
Connect to a SQL database (SQL Server, PostgreSQL, MySQL, etc.) for read-only introspection — listing databases, inspecting columns/keys, sampling rows. Read-only by default; DDL/DML needs explicit per-conversation approval and ships as a repo script with rollback. Use for any app/project whenever a task needs to query, introspect, or verify against the database.
Produce a full relational data-model document from an app's in-memory/demo models or an existing schema. Reads the real source (never invents), reshapes it into the house DB schema (tbl{Object}, abbreviated int PKs, f-prefixed FKs, join tables, audit columns), separates STORED vs DERIVED, and adds integrity constraints, indexes, finalize/lock immutability, and year-scoping. Optionally convenes the board (Elon + Tony Stark) for normalization & maintainability review. Outputs a self-contained HTML doc via html-doc-style into the project's _documentation/. Use when asked to "show / document / design the data model", "turn the demo data into a schema", or "what tables back this app".
Draw an entity-relationship / schema diagram as a self-contained inline SVG (no CDN, no image files, no mermaid) that drops straight into an HTML doc or stands alone. Renders each table as a colored-header box listing PK/FK/key columns, connects them with arrow-marker lines that point to the "many" side, color-codes relationships by layer, and adds a legend plus a collapsible ASCII fallback. Use when asked for a "schema diagram", "ER diagram", "data-model diagram", "draw the tables", or to add a visual to a data-model doc.
Convene your 3-person design board - "Elon Musk" (systems / architecture / data-model), "Steve Jobs" (taste & user experience), and "Tony Stark" (longevity & maintainability) - to spar with you on a new design or plan before you build. Each advisor reviews independently in parallel, then you get a synthesis of where they agree, where they clash, and the calls only you can make. Use when planning a new design or feature; invoke with /ask-the-board <what you are designing>.
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.