Showing 46261–46281 of 46281 skills
Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA accessibility, perceptually uniform color, tiered animation timing, and screenshot-driven visual validation at every stage. Use when: (1) creating or reviewing UI designs from an agent, (2) generating DESIGN.md for a project, (3) implementing designs from Pencil .pen files or Figma URLs, (4) enforcing visual quality standards on AI-generated interfaces, (5) setting up a multi-tool design pipeline, (6) converting between design tools and production code. Triggers on: 'design engineering', 'design system', 'DESIGN.md', 'premium design', 'high-end UI', 'pencil design', 'figma to code', 'stitch design', 'vibe design', 'visual design review', 'glass design', 'design tokens', 'UI quality'.
broomva/skills
Build or restyle anything in Liquid Dawn, the calm daylight sibling of Liquid Midnight. The look: warm paper grounds (Dawn, primary) and a sea-slate Dusk mode; nature drawn in type (lagoon caustics, meadow breeze, cumulus, pebble ripples on a one-glyph lattice); glyph-tile shoals of fish, birds and islands with cast shadows; dew glass rimmed in pearl liquid metal; refraction drawn by the field itself under glass; light, tight type in four switchable voices (Manrope, Inter Tight, Geist, Instrument) with one tide-blue payoff phrase; real proportional text laid out by pretext that ripples or reflows round moving shapes; and slow motion where every frame is a pure function of t. Ships tokens (OKLCH + hex, dawn and dusk modes), materials CSS, a framework-agnostic canvas kit (fields, ASCII + lenses, shoals, pretext pages, render loop), a live specimen, and a render-and-look tool. Use for calm landing pages and heroes, composer and chat surfaces, showcase moments, living backgrounds, reels and posts that should feel quiet, natural and premium. Triggers on "liquid dawn", "light liquid glass", "calm style", "paper style with glass", "nature ascii", "ascii shader landing", "ascii fish", "tranquil animation", "pearl rim", "light mode liquid midnight", "the calm variant", "liquid midnight but light". NOT for the dark expressive keynote look (that is liquid-midnight) or calm matte product chrome (broomva-design). Do not mix their tokens on one surface.
broomva/skills
Build or restyle anything in Liquid Midnight. The look: Apple Midnight blue-black grounds (hue 245-252, never purple), liquid glass rimmed in travelling liquid metal (a conic chrome edge with cyan, magenta and gold fringes), real WebGL glass plasma orbs, a quiet ASCII text-shader background, Raleway Light headlines with one blue payoff phrase, and spring motion where every frame is a pure function of t, so it renders to video. Ships tokens (OKLCH + hex), materials CSS, a framework-agnostic canvas/WebGL render kit, a starter scene, a style linter, a render-and-look tool, and Pencil shader fills. Use for keynotes and slides, 9:16 reels and 4:5 posts, landing sections, showcase cards in apps, living diagrams, and Pencil boards in this style. Triggers on "liquid midnight", "midnight blue style", "liquid glass and liquid metal", "chrome rim", "metal rim", "plasma orb", "orbloom", "ASCII shader background", "keynote style", "reel in our style", "the Agent Workspaces look", "showcase style". NOT for calm, matte product UI: that is broomva-design, an independent sibling, so do not mix their tokens. Never use the arcan-glass look for this.
broomva/skills
Tekton — the shared architecture-intent substrate for co-designing systems with the agent. One typed graph across six tiers (system / journey / data / infra / decisions / qualities); views are queries, not separate diagrams. The canonical artifact is a diff-friendly YAML model both human and agent read and write; it renders to Mermaid (agent-legible, GitHub-native) and a self-contained tabbed HTML viewer (human-visual). Cross-tier traceability (`tekton query <from> <to>`) answers "which infra does this user-journey step touch?" as a path query. USE WHEN: designing or thinking deeply about architecture, a system, a data model, user journeys/flows, or a technical plan WITH the agent; when a Category-C HTML doc isn't enough because you need to see AND edit AND traverse the design across tiers; "let's design X", "architect this", "model the system", "draw the flow", "how does this fit together", "diagram this", "/tekton". NOT FOR: a one-off throwaway diagram (use Mermaid inline); prose-only ADRs (write the ADR); implementation itself. Triggers on: design architecture, model the system, user journey, data model, tekton.
broomva/skills
Remove the "vibecoded" / AI-slop look from an arbitrary frontend codebase at the ROOT, autonomously, and prove the result clears a crafted floor. Full-repo traversal (any framework) → root-cause attribution (the one file that declares each default: font, icons, color/radius/shadow tokens, gradient/glass, motion, copy voice) → fix once at the root, never at forty call sites → the substance tells no detector covers (legal routes, loading/empty/error states, placeholder and fake content, real product evidence) → render at 1280+390 → deterministic gate (scripts/unslop_gate.py, exit 0 = clear). Composes the impeccable detector (64 rules) and commands, Anthropic frontend-design for direction, broomva-design as the house example; reimplements none of them. USE WHEN: a site or app "looks vibecoded", "looks AI-generated", "looks like every other AI site", "feels generic/templated/slop", "make it feel premium / crafted / intentional", "de-slop / unslop this", "does this pass the vibecoded test", or before shipping any LLM-built UI. NOT FOR: designing a new surface from scratch (impeccable new-work / frontend-design), a11y/perf audits alone (impeccable audit), backend-only repos, or a one-line style tweak.
broomva/skills
Personal finance and tax management substrate for Colombian residents. Imports bank transactions, tax certificates, and DIAN data. Projects annual tax liability (Form 210) with certificate-level accuracy. Handles password-protected PDFs from Colombian banks. Zero external paid services — all data stays local.
broomva/skills
Agentic finance engine for the Agent OS — x402 machine-to-machine payments, on-chain settlement, per-task revenue billing, and wallet management. Integrates with Arcan (agent runtime), Autonomic (economic homeostasis), and Lago (event-sourced persistence) to give agents real financial agency. Use when: (1) adding payment capabilities to an agent or agent-controlled API, (2) implementing x402 protocol support for HTTP-native machine payments, (3) wiring per-task billing so agents can charge for completed work, (4) managing agent wallets (secp256k1 keypair, encrypted storage), (5) configuring payment policies (auto-approve, spend caps, rate limits), (6) integrating Coinbase CDP or self-hosted facilitators for on-chain settlement, (7) bridging on-chain USDC with Autonomic's micro-credit state. Triggers on 'agent payments', 'x402', 'machine payments', 'agentic finance', 'haima', 'payment port', 'wallet management', 'per-task billing', 'USDC payments', 'agent revenue', '402 payment required'.
broomva/skills
Investment management skill — portfolio construction, analysis, and execution. Compounds finance-substrate (accounting/tax) + wealth-management (projections/goals) into a full financial framework. Covers traditional investing (stocks, ETFs, bonds), alternatives (crypto, prediction markets, real estate, VC), quantitative analytics (factor models, Monte Carlo, optimization), and platform integration (Alpaca, Coinbase, Polymarket, agent-browser for Colombian platforms). Embodies philosophies from Buffett, Dalio, Bogle, Munger, and Marks. Use when: (1) building or analyzing a portfolio, (2) screening stocks/ETFs/crypto, (3) running backtests or factor analysis, (4) executing trades or rebalancing, (5) tracking investments across platforms, (6) researching market data or fundamentals, (7) making investment decisions with structured frameworks. Triggers on 'investment', 'portfolio', 'stocks', 'ETF', 'bonds', 'crypto', 'trading', 'backtest', 'factor model', 'rebalance', 'Polymarket', 'Alpaca', 'asset allocation'.
broomva/skills
Wealth management, financial planning, and investment analytics skill. Compounds on finance-substrate for Colombian tax-optimized wealth building. Runs descriptive (portfolio health), predictive (compound growth projections, Monte Carlo), and prescriptive (allocation, rebalancing, tax-efficient withdrawal) analytics. Use when: (1) projecting long-term wealth growth, (2) optimizing asset allocation, (3) running scenario/stress tests on a portfolio, (4) planning tax-efficient contributions or withdrawals, (5) generating a wealth dashboard or net worth timeline, (6) goal-based financial planning (retirement, housing, education). Triggers on: 'wealth management', 'compound interest', 'asset allocation', 'portfolio projection', 'net worth forecast', 'retirement planning', 'investment strategy', 'rebalancing', 'monte carlo', 'financial plan'.
broomva/skills
Unifying control-systems metalayer for LLM-as-controller agent development. Bootstrap any repository with typed plant/action/trace schemas, safety shield conventions, multi-rate loop hierarchy, EGRI-compatible evaluator interfaces, and the full consciousness stack (governance + knowledge graph + episodic memory). Use when: (1) setting up agentic control primitives in a new or existing project, (2) designing LLM-as-controller architectures with safety shields and typed directives, (3) wiring EGRI/autoany loops for controller or artifact improvement, (4) bootstrapping the consciousness stack (control-metalayer + knowledge-graph + conversation bridge), (5) integrating symphony-style orchestration patterns, (6) defining plant interfaces, state estimators, or world models for agent-controlled systems, (7) user says "control kernel", "agentic control", "safety shield", "plant interface", "control metalayer", "agent controller", "multi-rate loop", "LLM control law".
broomva/skills
Distilled architecture & design principles for building self-service developer platforms, control-plane / data-plane separation, and edge-centralized cross-cutting concerns — drawn from a senior platform engineer's 8-year retrospective on building Atlassian's Envoy-based load-balancing platform (Open Service Broker + Sovereign xDS control plane + AWS infra + sidecar model). Covers the three IaC layers (image / infra / runtime), the template+context pattern for dynamic proxy configuration, forced-migration as an adoption tool, long-term maintenance discipline (churn as a smell, build vs maintain as distinct skills), and the non-technical engineering skills (diplomacy, mentoring vs teaching). Use when: (1) designing a self-service internal developer platform, (2) deciding between native proxy features vs sidecars, (3) introducing or migrating to Envoy / xDS / service mesh, (4) implementing the Open Service Broker spec or any resource-provisioning API, (5) abstracting cloud complexity (AWS CloudFormation, Packer, SaltStack/Ansible/Puppet) behind a developer-friendly API, (6) centralizing cross-cutting concerns (auth, authz, rate limiting, DDoS, access logs) at the edge, (7) planning a fleet-wide migration to new infrastructure, (8) auditing a long-lived codebase for churn / coupling / maintenance burden, (9) onboarding engineers to an existing platform, (10) deciding when to mentor vs train, (11) user says "platform engineering", "control plane", "data plane", "xDS", "Envoy", "service broker", "edge compute", "sidecar", "cross-cutting concerns", "self-service", "internal developer platform", "IDP", "platform migration", "code churn", "long-term maintenance", "mentoring vs teaching".
broomva/skills
Unattended multi-lens review of a plan, launch plan, spec, strategy doc, ADR or proposal. The autonomous counterpart to grill-with-docs: instead of interviewing the human, the agent asks the grilling questions itself and answers each one from evidence (repo docs, code, tickets, meeting notes, chat, live systems). Five review types run in a fixed order: drift (is every stateful claim still true, and was anything decided after the doc was written), grill (walk the decision tree, answer from evidence, keep a glossary and ADR candidates), ownership (every workstream and dependency has an owner, ticket and date), premortem, and a cross-model adversarial round scored on the FINAL text. Only the residue, decisions no reachable evidence can settle, goes back to the human, batched once, each with a recommended default. Use when the user asks whether a plan is "ready", "fully developed", "reviewed", "grilled", "adversarially verified", or says "review this autonomously", "grill it yourself", "run all the reviews", "autoreview", "/autoreview". NOT for a code diff alone (use code-review or cross-review) and NOT when the user wants to be interviewed live (use grill-with-docs).
broomva/skills
bstack primer — the Broomva Stack: twenty irreducible automation primitives (P1–P20) that turn an agent-driven workspace into a self-operating system. This is the AGENT-READABLE PRIMER (primitive contract + short-name index + when each fires), NOT the CLI. The bstack CLI + governance substrate (bin/, doctor, templates, hooks) is a separate product installed by clone + bootstrap (git clone https://github.com/broomva/bstack && ./bin/bstack bootstrap) — do NOT `npx skills add broomva/bstack` (it drops bin/scripts, the repo-root SKILL.md case of vercel-labs/skills#1523). Use this primer to reason with the primitives: Bridge (P1), Gate (P2), Tickets (P3), Pipeline (P4), Fanout (P5), Bookkeeping (P6), Freshness (P7), Janitor (P8), Wait (P9), Hygiene (P10), Empirical (P11), Persist (P12), Dream (P13), Dep-Chain (P14), Snapshot (P15), Crystallize (P16), Lens (P17), Audience (P18), Orchestrate (P19), Cross-Review (P20). Triggers on 'bstack', 'Broomva Stack', 'the primitives', 'P1'..'P20', 'primitive contract', 'bstack bootstrap', 'governance metalayer', 'self-operating workspace', 'how do I install bstack', 'what does Pn mean'.
broomva/skills
bstack P20 — Cross-Model Adversarial Review Gate. The model that wrote the code cannot be the final judge of the code. Before substantive PRs merge, fire a cross-model adversarial gate — different evaluator than writer, anti-slop scoring ≥7/10, a dynamic round budget (3 free, 4-7 earned by a continuation verdict carrying a falsifiable prediction, >=8 human), verdict logged in PR. Three strata: (A) Codex CLI cross-vendor for true different-model verdict, (B) fresh-context subagent under devils-advocate brief, (C) composed existing adversarial-review skills in parallel on code (a knowledge-only diff takes one stratum on a claims rubric). Use cross-review when: (1) about to push a substantive PR (>200 LOC OR public API OR multi-file OR governance-class), (2) reviewing a draft plan/design before implementation, (3) auditing a feature spec against single-model blind spots, (4) integrating with the /autonomous skill's pre-push gate. Triggers on 'cross-review', 'P20', 'adversarial review', 'anti-slop', 'cross-model gate', 'different evaluator', 'devils advocate gate', 'self-review prohibition'.
broomva/skills
Per-bstack-P11 reflex 7+16 — explicitly trigger the Dogfood Plan + per-stack cookbook + Dogfood Receipt sequence. Auto-detects the tech stack from repo signals (Cargo.toml + src-tauri/ → tauri-sidecar; next.config.* → nextjs; app.json + expo → expo-rn; Cargo.toml solo → rust-cli; openapi.* or REST framework deps → rest-api; mcp.{json,yaml} → mcp-server), loads the matching cookbook entry from bstack/references/dogfood-patterns.md (broomva/bstack ≥ 0.13.0), produces a six-row Dogfood Plan (entry surface · driver · evidence · smoke · end-to-end · receipt anchor), optionally executes via the named surfaces (Interceptor mandatory for visual deploy verification; gstack, cliclick, screencapture, curl+jq, xcrun simctl compose per stack), and produces the final receipt with binary anti-rationalization check. Three subcommands: /dogfood (full sequence — plan → execute → receipt), /dogfood plan (plan only), /dogfood receipt (receipt only, assumes plan exists in PR body or AGENTS.md). Inherits from broomva/bstack: cookbook, P11 discipline, stack-detection algorithm. Composes with broomva/autonomous (which fires this implicitly at reflex 7+16) — use /dogfood directly for narrower scope (small changes, exploration, pre-merge verification gate without full pipeline). USE WHEN dogfood, dogfood this, dogfood plan, dogfood receipt, validate as user, exercise the change, click through the app, /dogfood, P11 receipt, exercise like a user would, did I actually click it, prove this works for a user, interaction evidence, deploy verification. NOT FOR running CI checks (use /p9), batch headless automation (use Browser skill), or scientific-method experiment framing (use Science skill).
broomva/skills
Implement OpenAI Harness Engineering practices in any repository. Use when setting up or refactoring agent-first workflows, writing or upgrading AGENTS.md and PLANS.md, creating deterministic smoke/test/lint/typecheck harness commands, defining strict architecture boundaries and data-shape contracts, wiring observability from day 1, and adding entropy-control checks plus CI automation for reliable autonomous runs.
broomva/skills
Measure whether a codebase's verification actually touches the world, or whether it is checking itself. Keel gathers the verification edges it can read in a target (GitHub Actions, CircleCI, GitLab CI, Travis, package scripts, Makefile, Rakefile, pyproject and a dozen tool configs) — and reports the surfaces it recognised but could not parse, so blindness never passes for absence. It classifies each edge as anchored, self-referential, or unknown by asking whether the actor being verified can write to the signal's producer, and reports a grounding ratio. Novel cases are judged by the agent and then crystallized into probes — small reviewable scripts — so repeat shapes get cheaper every run. Then routes each ungrounded check to an anchored signal that already exists in the same graph. Use when: (1) auditing whether AI-generated or agent-maintained work is genuinely verified, (2) assessing how AI-native a codebase actually is — measured by what fraction of its verification the agents cannot author, (3) reviewing a CI/CD pipeline for circular verification, (4) someone claims tests pass and you want to know what that claim rests on, (5) measuring verifier independence. Triggers on keel, grounding ratio, grounded, is this actually verified, who checks the checker, circular verification, self-referential verification, verifier independence.
broomva/skills
Build or adversarially audit an evidence-first legal-readiness system for a software product, SaaS, AI app, API, marketplace, or website. Inventory every public and contractual claim; determine jurisdiction, operator, customer, data-role, payment-channel, and product-behavior applicability; compare prose with repository, live, vendor, registry, contract, and operational evidence; close authorized code/documentation gaps; and leave counsel, tax, filing, entity, and external-account blockers explicit. Use when asked for a legal audit, legal shield, SaaS legal baseline, terms/privacy/consent/payment review, compliance gap analysis, legal readiness, legal standing setup, product-claim substantiation, or to make an app legally safer before launch. NOT FOR giving legal advice, declaring a product compliant or legally secure, forming an entity, filing registrations or taxes, signing contracts, inventing operator facts, or replacing licensed counsel.
broomva/skills
The content contract for a design doc — what must be IN it, as against make-spec which owns how it LOOKS. Synthesised from five primary sources read verbatim (Lynch/Refactoring English + his worked example, Design Docs at Google, the Rust RFC template, Nygard's original ADR post, Oxide RFD 1). The load-bearing rule is the cost of reversing a decision, not its importance: a choice fixable in an afternoon is review noise, a one-way door left unargued is the failure a design doc exists to prevent. Two layers. DETERMINISTIC — `scripts/spec_check.py` reads a markdown or HTML doc and decides 18 findings: required sections by class not by name, status resolvable and supersession pointed, >=2 alternatives with a stated reason for rejection somewhere in the section, non-goals that are declined goals rather than negated requirements, drawbacks that state a cost, acceptance that carries a number or a runnable command, and an implementation-manual detector for a doc with no trade-off language anywhere. JUDGMENT — `references/rubric.md` grades the five things a script cannot: whether the documented decisions are the expensive ones, whether the alternatives are real or strawmen, whether the non-goals are load-bearing, whether trade-offs are argued or merely mentioned, and whether the first screen is legible to the widest expected reader. Use when: (1) writing or reviewing a spec, plan, ADR, RFD or design doc, (2) deciding whether something warrants a design doc at all, (3) gating a doc before it goes out for review, (4) asked what belongs in a spec or why a spec is weak. Triggers on 'spec contract', 'design doc', 'write a spec', 'review this spec', 'is this spec any good', 'what belongs in a design doc', 'ADR', 'RFD', 'non-goals', 'alternatives considered', 'spec review', 'spec gate', 'design review', 'one-way door', 'reversal cost'.
broomva/skills
Audit and rightsize a context surface — CLAUDE.md, AGENTS.md, a SKILL.md, a system prompt, or a single prompt — against the Claude-5 context-engineering reversals. Measures the surface (token budget, how much of it is phrased as hard rules vs judgment, near-duplicate sections, contradiction candidates, filesystem-derivable content, progressive-disclosure gaps), then adjudicates each section keep / relocate / delete using a grounding-aware predicate: prose backed by an independent mechanism is decorative and free to cut, prose that is the only carrier of a behavior is a real bet. Also rewrites prompts and skills from prohibition-form into judgment-form. Anthropic deleted >80% of Claude Code's system prompt for Claude 5 with no eval loss; this is the repeatable version of that cut. Use when: (1) a CLAUDE.md or AGENTS.md has grown and you want to know what is safe to remove, (2) an agent is ignoring or colliding with its own instructions, (3) a prompt is long and over-constrained and underperforming, (4) auditing a skill for over-constraint before publishing, (5) onboarding a repo whose agent context was written for an older model. Triggers on unhobble, rightsize, trim my CLAUDE.md, audit my CLAUDE.md, is my CLAUDE.md too long, context engineering, prune governance, over-constrained, improve this prompt, my agent ignores instructions, conflicting instructions, prompt too long.
broomva/skills
Personalized cancer treatment navigation — maximal diagnostics, parallel therapy, therapeutic development, structure-based protein design. Use when (1) researching cancer treatments or combinations, (2) designing diagnostic strategies, (3) evaluating neoantigen vaccines or radioligand therapies, (4) navigating FDA expanded access or IRB processes, (5) interpreting ctDNA/MRD data, (6) building bioinformatics pipelines, (7) scRNA-seq target discovery, (8) AlphaFold/RFdiffusion/ProteinMPNN for neoantigen validation or de novo binder design, (9) patient advocacy. Keywords — cancer, oncology, neoantigen, vaccine, immunotherapy, radioligand, ctDNA, scRNA-seq, FAP, AlphaFold, RFdiffusion, ProteinMPNN, personalized medicine.
broomva/skills