igorwarzocha
- 82 skills
- 0 followers
- 412 repo stars
- last month last updated
- ▌ Skill Creator 3 · igorwarzocha bundleDesigns, writes, refactors, and packages agent skills for this workspace. Use when the user asks to create a new skill, improve an existing `SKILL.md`, tighten trigger descriptions, split heavy detail into `references/` or `scripts/`, add examples or validation, or port a workflow into a reusable skill. Do not use for one-off prompt tweaks, strict deployment runbooks, or vague workflows that are not repeatable yet.
- ▌ Skill Creator 2 · igorwarzocha bundleDesigns, audits, refactors, and packages reusable agent skills. Use for creating or improving SKILL.md files, trigger descriptions, supporting references/scripts/assets, examples, validation, consolidation, or porting skills between agents. Not for one-off prompt edits, strict project procedures, or passive documentation with no repeatable workflow.
- ▌ Gh Issue Pr Flow 2 · igorwarzochaRuns a lightweight GitHub issue and PR workflow with gh. Use when the user asks to create or update GitHub issues, work from an issue number or PR link, create a branch, push changes, open a PR, request review, or handle PR review feedback. Repository-specific instructions override this global fallback when present.
- ▌ Agent Native Hardening 2 · igorwarzocha bundleHardens codebases for agent-native maintainability across languages. Use when asked to audit, score, refactor, or plan cleanup for architecture, godfiles, godfunctions, feature folders, duplication, type/contract safety, traversability, feedback loops, worktrees, or subagent-friendly structure.
- ▌ Agent Pages · igorwarzochaCreate or update rich task/session artifacts in the local Agent Pages app. Use when the user asks for a visual proposal, options, prototype, diagram, report, review surface, or anything easier to judge/annotate than chat.
- ▌ Background Process · igorwarzochaHousekeeping guide for background process tools. You SHOULD load this skill before launching background processes to avoid stale processes, port conflicts, and buffer issues. Examples: - user: "Start the dev server" → load skill, then launch with proper cleanup practices - user: "Run npm run dev" → load skill to verify startup and use meaningful IDs - user: "What background processes have we launched?" → check for duplicate processes, port conflicts
- ▌ Plans And Specs · igorwarzochaThis SKILL provides detailed instructions on how to use the planning plugin tools. MUST be loaded when: Situations: - User asks to create a plan, roadmap, or break down work into steps - User mentions specs, requirements, or standards that need to be documented - User references an existing plan that needs to be read or updated - User asks to mark work as complete or done - User wants to link requirements to a plan - User references a task that matches <available_plans>
- ▌ Workflows · igorwarzochaLoad and create repository SOPs via `workflows` and `workflows_create` tools. Use proactively when executing repo-specific procedures, documenting repeatable processes, or when `<available_workflows>` contains matching entries. Examples: - user: "Release a new version" -> check available_workflows, load matching SOP, follow steps - user: "How do we deploy?" -> call workflows to list, load relevant procedure - user: "Document this process" -> use workflows_create to capture the SOP - user: "Create a migration workflow" -> use workflows_create with structured body - user: "Don't make the same mistake again" -> use workflows_create to the correct workflow
- ▌ Update Apply Patch Source · igorwarzochaRefreshes the vendored Rust apply_patch source from the local Codex checkout, rebuilds the binary, and validates the package without publishing locally.
- ▌ Opencode Server Launcher · igorwarzochaLaunch and manage OpenCode servers with simple commands, from single instances to multi-server swarms
- ▌ Opencode Orchestrator Creator · igorwarzochaCreates universal OpenCode orchestrator folder structure with specialized agent that can manage swarm servers via curl commands
- ▌ Openbrain Setup · igorwarzocha bundleSet up openbrain-local-convex from a cloned repository on localhost, a LAN server, or LAN client machines. Use when the user asks to install, bootstrap, deploy, repair services, validate health, or make `brain` work end-to-end without handwaving.
- ▌ Openbrain Operator · igorwarzocha bundleOperate and troubleshoot OpenBrain memory through the `brain` CLI and OpenBrain HTTP API. Use when the user asks to capture thoughts, run semantic search, review recent/history, check stats/health, tune retrieval, or diagnose why memory read/write is failing.
- ▌ Replicate Todo Gui Behavior 1 1 · igorwarzochaReproduce pi-masterplan todo selector/action UX, layout anchoring, and key behavior in another extension command.
- ▌ Clawa Ops · igorwarzocha bundleOperates and repairs a Clawa home. Use for creating or onboarding subclawas, editing .pi/claw.jsonc, managing pulses, maintaining CLAWAS.md routing and living docs, importing OpenClaw or Hermes context, or diagnosing home structure. Not for ordinary project code or work that belongs inside an established specialist lane.
- ▌ Clawa Vault · igorwarzochaMaintains a Clawa home's shared vault as a tidy, linked second brain. Use when saving durable knowledge, integrating research, finding what the home already knows, curating or reorganizing vault pages, repairing navigation, or promoting repeated memory into a reusable concept. Do not use for raw momentary memory, identity docs, task scratchpads, or documentation owned by a source-code project.
- ▌ Warmth Pass · igorwarzochaWarms stiff internal agent docs without losing rules, paths, commands, tool names, boundaries, or facts. Use for AGENTS.md, CLAW.md, HUMAN.md, CURIOUS.md, persona cards, worker-home docs, or project instructions that feel robotic. Do not use for schemas, runbooks, API specs, or grammar-only cleanup.
- ▌ Act1 · igorwarzocha bundleUse this at the start of Act 1 and for Act 1 route, reward, elite, boss, and survival decisions. Trigger it on new runs, whenever Act 1 pathing changes, before Act 1 elite or boss commitments, and when documenting new Act 1 encounters.
- ▌ Act2 · igorwarzocha bundleUse this at the start of Act 2 and for Act 2 route, reward, elite, boss, and survival decisions. Trigger it when Act 2 begins, whenever Act 2 pathing changes, before Act 2 elite commitments, and when documenting new Act 2 encounters.
- ▌ Combat · igorwarzocha bundleUse this for combat turn planning and execution. Trigger it before taking combat turns, when deciding whether a turn is easy or hard, when a fight presents setup vs tempo tension, when cost changes or free-card effects appear, and whenever you need general combat heuristics that are not boss-or-elite specific.
- ▌ Events · igorwarzocha bundleUse this when the current screen is an event or when planning an event line from the real run state. Trigger it before choosing any event option, especially when the event offers generated cards, relics, gold-for-HP trades, removes, transforms, or branch-defining risk/value choices.
- ▌ Ironclad · igorwarzocha bundleUse this when the current run is Ironclad. Trigger it on new runs, after automated compaction summaries, and for Ironclad card, route, shop, reward, and combat decisions.
- ▌ Merchant · igorwarzocha bundleUse this when the current screen is a merchant or when planning a shop line from map pressure, gold, deck state, relics, and potions. Trigger it before buying, before leaving a shop, and when a forced elite or boss makes the shop an immediate survival checkpoint. Shops are hard decisions, so prefer reading them with `--hard`.
- ▌ Act Start · igorwarzocha bundleUse this at the start of an act, or whenever act-level planning resets after a compaction summary or major state change. Trigger it to re-evaluate deck shape, route goals, elite readiness, and act-specific priorities.
- ▌ Learning Loop · igorwarzocha bundleUse this when playing in this repo and you need to keep the run log, reference notes, mechanic notes, and strategy notes updated as durable learning. Trigger it during live runs, immediately after meaningful floors, immediately after elite or boss fights and boss rewards, when a new boss/elite/event/mechanic appears, when a fight needs STS1 parallels to understand what it is testing, and when ending a run so the post mortem can be reconciled against Compendium -> Run History before the final rewrite.
- ▌ Boss And Elite Fights · igorwarzocha bundleUse this when planning for, entering, or playing an elite or boss fight. Trigger it before pathing into hard fights, before committing combat lines in elites or bosses, when the hard fight is new or unclear and needs STS1 parallel reasoning, and after those fights when updating durable lessons.
- ▌ Effect · igorwarzocha bundleOpinionated guide for building production TypeScript applications with Effect v4. Use when implementing Effect workflows, services, layers, schemas, configuration, schedules, caches, streams, HTTP clients, or tests.
- ▌ Gh Stack · igorwarzochaManage GitHub stacked pull requests with `gh stack`. Use when creating stacked diffs, splitting work into dependent PRs, pushing/submitting/syncing/rebasing a stack, checking stack status, or navigating branch layers. Do not use for ordinary single-branch PR work.
- ▌ Gh Issue Pr Flow · igorwarzocha bundleRuns this repo's GitHub issue and PR workflow with gh. Use when the user mentions issue numbers, PR links, or the project board, asks to pick a manageable issue, wants an issue rewritten into a proper issue, wants backlog triage or relabeling, or wants a PR opened, updated, or reviewed. Do not use for local-only git work with no GitHub issue or project flow.
- ▌
- ▌ Agent Native Hardening · igorwarzocha bundleTypeScript/JavaScript codebase hardening: maintainability, code quality, architecture cleanup, repo scoring, agent-friendly structure, godfiles, godfunctions, feature folders, DRY, type safety, traversability, feedback loops, worktrees, subagents, swarm refactors.
- ▌ Howcode Dual Native Extension · igorwarzocha bundleDeprecated. Howcode now uses regular Pi SDK extensions from Pi settings/packages; do not add Howcode-only native extension snapshots or settings. Use this only as historical context when removing old dual-native-extension code.
- ▌ Build And Run Temp Howcode · igorwarzochaUse when Igor asks to build this branch/current repo and run a disposable build version
- ▌ Temporary UI Mock Fixtures · igorwarzochaHow to add short-lived static fixtures for hard-to-reproduce UI states while tuning layout
- ▌ Worktree Completion Summary · igorwarzochaUse when Igor says a worktree seems complete and wants a branch/worktree summary saved for later review and merging
- ▌ Debug Weird UI Behavior With Cdp Logging · igorwarzochaUse when weird app/UI behavior needs live reproduction and tracing, including flicker, stale state, remounts, focus/scroll jumps, action glitches, or ordering flashes
- ▌ Pi Stuff Delivery · igorwarzocha bundleRead after general repository delivery when shipping package changes, preparing a release PR, or updating a dependent release batch.
- ▌ Pi Stuff Release Stack · igorwarzocha bundleRead after general repository delivery when dependent package work uses a JJ-managed native stack with one cumulative umbrella.
- ▌ Pi Stuff Prompt Caching · igorwarzocha bundleRead after general prompt-caching guidance when investigating or changing this repo's Codex cache, continuation, prewarm, replay, or compaction.
- ▌ Pi Stuff Tool Contracts · igorwarzocha bundleRead after general agent-tool design when reviewing or changing a model-facing Pi extension tool in this repository.
- ▌ Pi Stuff Tool Error Audit · igorwarzocha bundleRead when auditing tool and Notebook failures across stored Pi sessions or checking recovery since this repo's previous audit.
- ▌ Scratchpad · igorwarzochaRead before putting experimental or disposable work that should survive the session into the persistent scratchpad.
- ▌
- ▌ Chrome Cdp · igorwarzocha bundleChrome CDP inspection/control: rendered pages, authenticated tabs, navigation, interaction, DOM/accessibility state, network, screenshots. Use when browser-rendered evidence or existing browser state matters.
- ▌
- ▌
- ▌ Repository Delivery · igorwarzocha bundleRead before recording or delivering repository work through commits, GitHub issues, or pull requests.
- ▌
- ▌ Omarchy Help · igorwarzocha bundleRead before changing, diagnosing, maintaining, or recovering an Omarchy Quattro workstation.
- ▌
- ▌ Prompt Caching · igorwarzochaRead before designing, measuring, or debugging prompt-cache behaviour in an agent harness or extension.
- ▌
- ▌ Agent Tool Design · igorwarzocha bundleRead before creating, reviewing, or refining a tool exposed to an agent.
- ▌ Harness Checklist · igorwarzochaRead before auditing a coding-agent harness environment and recommending improvements.
- ▌ Instruction Calibration · igorwarzochaRead before empirically tuning a reusable skill or agent prompt.
- ▌ Agent Session Diagnostics · igorwarzochaRead before diagnosing a coding-agent session or recurring skill or tool failure that drifted, looped, ignored intent, or behaved unexpectedly.
- ▌ PDF · igorwarzocha bundleHandle PDF manipulation, form filling, text/table extraction, and high-fidelity generation. Use for professional PDF reports, merging documents, and automated form processing. Use proactively when visual quality and verification are critical. Examples: - user: "Fill this PDF form and verify" -> populate fields and inspect images - user: "Merge these reports and add a watermark" -> use pypdf - user: "Extract this complex table to Excel" -> use pdfplumber for layout preservation
- ▌ Word · igorwarzocha bundleHandle Word document (.docx) creation, editing, and analysis with high-fidelity visual review. Use for professional reports, legal documents, and tracked changes. Use proactively when quality and precise formatting are critical. Examples: - user: "Create a professional report in Word" -> use python-docx with render loops - user: "Draft a legal contract with redlines" -> use ooxml redlining workflow - user: "Extract text from this DOCX while preserving structure" -> use pandoc markdown conversion
- ▌ Comms · igorwarzocha bundleApply standardized formats for internal business communications. Use for status reports, company newsletters, FAQs, and leadership updates. Use proactively when consistency in corporate communication is required. Examples: - user: "Write a 3P update for the week" -> use Progress/Plans/Problems template - user: "Draft a company-wide announcement" -> use newsletter format - user: "Create an FAQ for the new project" -> use internal FAQ guidelines
- ▌ Excel · igorwarzocha bundleHandle spreadsheet operations (Excel/CSV) with high-fidelity modeling, financial analysis, and visual verification. Use for budget models, data dashboards, and complex formula-heavy sheets. Use proactively when zero formula errors and professional standards are required. Examples: - user: "Build an LBO model" -> create Excel with banking-standard formatting - user: "Analyze this data and create a dashboard" -> use openpyxl + artifact_tool - user: "Verify formulas in this spreadsheet" -> run recalc.py to check for errors
- ▌ Skill Creator · igorwarzocha bundleArchitect and refine OpenCode skills to extend agent capabilities. Handles directory scaffolding, SKILL.md authoring, frontmatter optimization, and resource organization (scripts/references/assets). Use proactively for creating new skills, updating existing workflows, or fixing skill discovery issues. Examples: - user: "Create a new skill for database management" → scaffold directory and initial SKILL.md - user: "My skill isn't triggering correctly" → analyze and refine frontmatter description - user: "Add a python script to the image-processing skill" → structure scripts/ directory - user: "How should I structure a skill for API docs?" → design references/ layout
- ▌ Cowork · igorwarzochaPrinciples and patterns for effective collaborative work (coworking). Use for aligning agents on communication etiquette, workspace hygiene, and feedback loops. Use proactively when coordinating multi-agent workflows, managing vault hygiene, or standardizing status updates. Examples: - user: "How should we work together?" -> review coworking principles - user: "Give me a status update" -> use 3P status reporting pattern - user: "Keep the workspace clean" -> apply vault hygiene rules - user: "Coordinate the specialists" -> follow collaboration patterns
- ▌ Themes · igorwarzocha bundleApply professional visual themes to documents and presentations. Use for styling artifacts with consistent color palettes and font pairings. Use proactively to quickly improve the aesthetic quality of deliverables. Examples: - user: "Apply a modern theme to this deck" -> use Modern Minimalist theme - user: "I want a tech aesthetic for this doc" -> apply Tech Innovation theme - user: "Create a custom theme for my project" -> generate new color/font specification
- ▌ Writing · igorwarzochaHandle structured co-authoring of professional documentation. Use for proposals, technical specs, and RFCs. Use proactively when a collaborative drafting process (Gathering -> Refinement -> Testing) is needed. Examples: - user: "Draft a technical RFC for the new API" -> follow Stage 1 context gathering - user: "Refine the introduction of this proposal" -> use iterative surgical edits - user: "Test if this document is clear for readers" -> run reader testing workflow
- ▌ Command Creator · igorwarzochaCreate custom /slash commands for repetitive tasks. Use proactively for command creation, prompt automation, or workflow shortcuts. Examples: - user: "Make a /test command that runs pytest" → create command in opencode.json, set prompt to run tests with bash tool - user: "Add a /review command for PRs" → design prompt to fetch diff, analyze changes, generate review comments - user: "Automate this repetitive task" → identify pattern, create slash command with parameterized prompt - user: "Make a /deploy command" → design workflow (build, test, deploy), encode in command prompt
- ▌ Branding · igorwarzochaApply official brand colors and typography to professional artifacts. Use for presentations, reports, and documents to ensure corporate visual identity. Use proactively when a "client-ready" look-and-feel is requested. Examples: - user: "Brand this report" -> apply corporate colors and fonts - user: "Apply brand guidelines to these slides" -> update colors/fonts in XML - user: "Check if this document is on-brand" -> verify against color/font standards
- ▌ Repo Maintenance · igorwarzocha bundleMaintain repository integrity and documentation. Use for auditing structure, checking config validity, and reviewing inventory. Use proactively to validate the repository or sync documentation. Examples: - user: "Validate the repo" → run audit_repo.py - user: "Check agents" → run audit_repo.py, review errors - user: "Update documentation" → run sync_docs.py - user: "Check for issues" → run full audit
- ▌ Powerpoint · igorwarzocha bundleHandle PowerPoint (.pptx) creation, design, and analysis. Use for pitch decks, status updates, and visual storytelling. Use proactively when precise layout positioning and design principles are needed. Examples: - user: "Create a 10-slide deck for the board meeting" -> use design principles + html2pptx - user: "Convert this report into a presentation" -> extract text and map to template - user: "Audit this deck for layout issues" -> generate thumbnail grid for inspection
- ▌ Agent Architect · igorwarzocha bundleCreate and refine OpenCode agents via guided Q&A. Use proactively for agent creation, performance improvement, or configuration design. Examples: - user: "Create an agent for code reviews" → ask about scope, permissions, tools, model preferences, generate AGENTS.md frontmatter - user: "My agent ignores context" → analyze description clarity, allowed-tools, permissions, suggest improvements - user: "Add a database expert agent" → gather requirements, set convex-database-expert in subagent_type, configure permissions - user: "Make my agent faster" → suggest smaller models, reduce allowed-tools, tighten permissions
- ▌ User Onboarding Sop · igorwarzochaGenerate AGENTS.md for end-user assistance. Covers setup, installation, running, and troubleshooting. Use proactively when user asks for "getting started" help or during /init user workflow. Examples: - user: "/init user" → user assistance AGENTS.md with official docs - user: "Create getting started guide" → installation + setup + troubleshooting - user: "Document how to use this repo" → user-focused AGENTS.md - user: "Help users run this software" → setup, prerequisites, usage patterns
- ▌ Agent Navigation Sop · igorwarzochaGenerate AGENTS.md for AI agent navigation. Covers build/test commands, coding conventions, task routing, and codebase structure. Use proactively during /init workflow or when creating agent-readable repository documentation. Examples: - user: "/init" → full AI navigation AGENTS.md + skill recommendations - user: "/init basic" → minimal AGENTS.md structure only - user: "Create AGENTS.md for this repo" → assess complexity, generate navigation doc - user: "Document codebase for AI agents" → structured AGENTS.md with task routing
- ▌ Security Bun · igorwarzocha bundleReview Bun runtime security audit patterns. Use for auditing Bun-specific vulnerabilities including shell injection, SQL injection, server security, and process spawning. Use proactively when reviewing Bun apps (bun.lockb, bunfig.toml, or bun:* imports present). Examples: - user: "Review this Bun shell script" → audit `$` usage and argument injection - user: "Check my bun:sqlite queries" → verify `sql` tagged template usage - user: "Audit my Bun.serve() setup" → check path traversal and request limits - user: "Is my Bun.spawn() usage safe?" → audit command injection and input validation - user: "Review WebSocket security in Bun" → check authentication before upgrade
- ▌ Security Django · igorwarzocha bundleReview Django security audit patterns for settings and middleware. Use for auditing SECRET_KEY, DEBUG, CSRF, and auth decorators. Use proactively when reviewing Django apps (settings.py or manage.py present). Examples: - user: "Audit my Django settings.py" → check SECRET_KEY, DEBUG, and ALLOWED_HOSTS - user: "Check Django views for auth" → verify @login_required and permission classes - user: "Review Django CSRF config" → check middleware and @csrf_exempt usage - user: "Scan for SQL injection in Django" → find raw SQL usage instead of ORM - user: "Audit Django REST framework config" → check default permissions and auth
- ▌ Security Docker · igorwarzocha bundleReview Docker and container security audit patterns. Use for auditing secrets in layers, port exposure, and non-root users. Use proactively when Dockerfile or docker-compose.yml is present. Examples: - user: "Audit this Dockerfile" → check for secrets in ENV/ARG and non-root USER - user: "Review docker-compose ports" → find accidentally exposed databases - user: "Check for secrets in image history" → audit layers and build artifacts - user: "Optimize Docker security" → implement multi-stage builds and minimal base images - user: "Audit container privileges" → check for privileged: true or docker.sock mounts
- ▌ Security Secrets · igorwarzocha bundleReview secret detection patterns and scanning workflows. Use for identifying high-signal secrets like AWS keys, GitHub tokens, and DB passwords. Use proactively during all security audits to scan code and history. Examples: - user: "Scan for secrets in this repo" → run high-signal rg patterns and gitleaks - user: "Check for AWS keys" → scan for AKIA patterns and server-side exposure - user: "Audit my .env files" → ensure secrets are gitignored and not committed - user: "Verify secret redaction" → check that reported secrets follow 4+4 format - user: "Scan build artifacts for keys" → search dist/ and build/ for secret patterns
- ▌ Component Engineering · igorwarzocha bundleApply the formal standard for React component engineering focusing on accessibility, composition, and styling. Use for building professional, composable React artifacts. Use proactively when creating or reviewing React components. Examples: - user: "/component-create Button trigger" → build accessible button with asChild and keyboard map - user: "/component-review src/components/Input.tsx" → audit for accessibility and composition compliance - user: "Build a responsive slider" → select taxonomy type and implement with data attributes - user: "Review my layout component" → check for monolithic patterns vs composition
- ▌ Convex Auth · igorwarzochaImplement Convex authentication and authorization patterns with OIDC providers or Convex Auth. Use for auth provider setup, ctx.auth usage, user identity handling, and auth-aware schema patterns. Use proactively when users mention auth, JWT, Clerk/Auth0/WorkOS, or Convex Auth. Examples: - user: "Add auth to Convex" → choose provider and outline setup - user: "Get current user" → use ctx.auth.getUserIdentity and checks - user: "Service-to-service access" → use shared secret pattern
- ▌ Convex Core · igorwarzochaBuild Convex schemas, queries, mutations, actions, and client usage with strict validators and indexes. Use for data modeling, function authoring, argument/return validation, and performance guidance. Use proactively when work touches convex/schema.ts, functions, or api.* references. Examples: - user: "Design tables for multi-tenant app" → defineSchema/defineTable with indexes - user: "Write a mutation" → args/returns validators + auth checks - user: "Optimize query" → add index and withIndex range expression - user: "Use useQuery" → show generated hook usage
- ▌ Convex Deploy · igorwarzochaImplement Convex deployment workflows, environments, and CI/CD configuration. Use for dev/prod/preview deployments, deploy keys, local deployments, environment variables, schema/index rollout safety, and HTTP action URLs. Use proactively when users mention deploy, preview, staging, CI, env vars, or local backend. Examples: - user: "Set up Convex deploy in CI" → configure deploy key + npx convex deploy steps - user: "How do preview deployments work?" → explain preview keys, lifecycle, limits - user: "Deploy to prod safely" → list safe schema/function change patterns - user: "Use local convex" → explain npx convex dev --local and limitations
- ▌ Convex Runtime · igorwarzochaImplement Convex runtime features: HTTP actions, file storage, search (full text + vector), scheduling (crons + scheduled functions), and RAG patterns. Use for webhooks, uploads, search indexes, vectorSearch actions, and background workflows. Use proactively when users mention HTTP endpoints, files, search, embeddings, or cron/schedule. Examples: - user: "Add full text search" → define searchIndex + withSearchIndex query - user: "Upload files" → generate upload URL and persist storageId - user: "Vector search" → action with ctx.vectorSearch and doc fetch - user: "Run cleanup nightly" → cronJobs + function reference
- ▌ Convex Components · igorwarzocha bundleUse Convex Components to add isolated backend features and compose component APIs. Use for installing components, calling component APIs, authoring components, and handling component-specific constraints (Id types, env vars, pagination, auth). Use proactively when users mention components, workpool, workflow, agent component, or reusable backend modules. Examples: - user: "Install the Agent component" → add convex.config.ts + use() + components API - user: "Call component functions" → ctx.runQuery(components.foo.bar, args) - user: "Build a component" → defineComponent, schema, _generated, packaging - user: "Expose component API to clients" → re-export functions with auth
- ▌ Vite Shadcn Tailwind4 · igorwarzochaInitialize shadcn/ui + Tailwind CSS v4 in Vite projects (Vite-specific, not Next.js/Remix). Use proactively for Vite project setup, shadcn component installation, or Tailwind v4 configuration. Examples: - user: "Setup shadcn in my Vite project" → install deps, configure tailwind v4 CSS-first, init shadcn, verify components work - user: "Add shadcn to existing Vite app" → check existing config, install CLI, add components.json, update CSS imports - user: "Use Tailwind v4 with shadcn" → configure @import with @theme, remove v3 config, setup custom tokens - user: "Create Vite + React + shadcn project" → scaffold Vite, install shadcn, configure theme, add sample components