Claude Skills by jaydubya818

Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identit...

Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Umbrella skill for integrating an agent with Mission Control, the orchestration and observability control plane. Use this skill when an agent needs to interact with Mission Control and you must route to the right focused skill — registration, heartbeats, task lifecycle, approvals, deliverables, memory, budget, or run logging. All interactions use Convex mutations and queries; there is no REST API.

Walk through the registry lifecycle for a single SKILL package — the same loop Tessl documents, implemented in Mission Control.

Ship skill changes with evidence, not intuition.

Use when a non-trivial change needs types and module boundaries designed before code.

Use when an important artifact needs independent solutions compared and synthesized.

Use when the user wants working preferences captured in a reusable mode skill.

Use when an authorized pull request needs ongoing CI and review follow-through.

Capture before/after screenshots of pages, elements, or images. Use when UI changes need visual comparison or pull-request evidence.

Use when a change needs downstream risks traced and its key safety assumption proved.

Use when the previous technical answer needs a direct, jargon-free restatement.

Separate orchestration from reusable mechanics while preserving transactions. Use when workflows duplicate operational logic.

Use when a repository needs a repeatable driver that proves real UI, CLI, or service behavior.

Use when code needs generated clutter removed and structure simplified without behavior changes.

Capture observable runtime proof with video, screenshots, or measured output. Use when a change needs evidence beyond test reports.

Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.

Use when failing pull-request checks need a root-cause fix and a verified rerun.

Use when a branch needs conflicts resolved and the merged result verified.

Use when pull-request feedback needs to be fetched and summarized for action.

Run greploop through @greptile-apps when the normal trigger rejects a large PR. Use only with the companion greploop skill.

Run bounded Greptile review-and-fix cycles on a PR, MR, or shelved change. Use when Greptile is an explicit delivery gate.

Use for runtime, ownership, layering, code-walkthrough, and placement questions.

Use when a change's assumptions, evidence, or design need adversarial review.

Use when a project's verification driver or feature map may be stale.

Use when a correct pull request needs clearer history, description, or reviewer guidance.

Tracks and enforces agent spend in Mission Control. Use this skill when recording costs via api.agents.recordSpend, declaring budgetDaily and budgetPerRun limits at registration, or reacting to budgetRemaining and budgetExceeded values returned by the heartbeat before spending more money.

Preserve Mission-to-release lineage, evidence, and authority boundaries. Use when Mission Control or a similar software factory governs the work.

Keeps an agent alive in Mission Control by calling the api.agents.heartbeat mutation every 30-60 seconds. Use this skill when running any agent session: agents that miss heartbeats for 2 minutes get quarantined, and the heartbeat response is how you discover pending tasks, approvals, and budget state.

Persists agent knowledge across sessions using the Mission Control agent documents system. Use this skill when depositing session memory before shutting down, keeping a WORKING_MD scratchpad up to date, writing daily notes, or reading back previously stored memories at session start.

Registers an agent with Mission Control via the Convex api.agents.register mutation. Use this skill when an agent session starts and the agent must announce itself (name, emoji, role, workspace, task types, budgets) before doing any other work. Re-registering an existing agent updates its heartbeat.

Requests human or dual-control approval for risky actions through the Convex api.approvals.request mutation. Use this skill when an action is YELLOW or RED risk tier — YELLOW needs a single approval, RED needs dual control (two decisions), and GREEN/LOW actions auto-approve. Poll status before acting.

Records every agent execution turn as a run in Mission Control. Use this skill when starting a run (status RUNNING), completing or failing one (COMPLETED / FAILED), and reporting model, token counts, and cost so the observability and audit trail stays honest across all agent activity.

Submits finished work to Mission Control as content drops and posts progress to task threads. Use this skill when a piece of work is complete and needs human review, or when you should communicate progress, questions, or artifacts on a task — don't just complete tasks; submit the actual work.

Drives tasks through the Mission Control state machine: find INBOX tasks, assign yourself, and transition through ASSIGNED, IN_PROGRESS, REVIEW, and DONE. Use this skill when claiming, creating, or progressing a task — every status change must go through api.tasks.transition with an idempotency key.

Create or use a task-owned Git worktree for repository edits. Use for features, fixes, or documentation changes; skip read-only work.

Use when code comments need structural review, root-cause fixes, and constraint encoding.

Use when non-trivial work should follow the smallest rigorous Jstack workflow.

Apply when repeated fixes fail and a shared assumption may be wrong.

Apply when validation or adapters leak from external boundaries into core logic.

Apply when a rerunnable script, codemod, generator, or check makes work auditable.

Apply when a repeated instruction should become enforceable in tests, lint, metadata, or tools.

Apply when a novel design needs concrete candidates compared before selection.

Apply when scope threatens a polished, clear, and trustworthy user experience.

Apply when a workaround would hide a defect that can be reproduced and traced.

Apply when core types, data structures, or shared-state boundaries will shape the system.