jal-co

@jal-co source repo

62 skills
0 followers
16 hours ago last updated

▌
Writing Skills · jal-co bundle
Use when explicitly requesting test-driven skill authoring or pressure-scenario validation. Default skill-authoring guidance is emil-writing-skills.

0
installs
▌
Port Claude Plugin · jal-co
Port an existing Claude Code plugin to a portable ap-sdk definePlugin that compiles to every harness (Codex, Gemini, Copilot, Cursor, Windsurf, Pi, OpenCode). Use when the user has a .claude-plugin/ (agents/, commands/, hooks/, skills, CLAUDE.md, companion files) and wants it to run on other coding agents, or asks to "port", "convert", or "make my Claude plugin work everywhere".

0
installs
▌
Hermes Webclaw · jal-co bundle
Hermes Agent plugin that replaces the bundled Firecrawl plugin with native WebClaw v1 API support — search, scrape/extract, and crawl. Install when the user wants to use WebClaw as their web backend in Hermes, set up WEBCLAW_API_KEY, or switch from Firecrawl to WebClaw.

0
installs
▌
Frontend Design · jal-co bundle
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

0
installs
▌
Components Build · jal-co bundle
The canonical standard for building React components. Covers composition, accessibility, typing, styling, state, polymorphism, asChild, data attributes, design tokens, and artifact taxonomy from the components.build specification by Hayden Bleasel and shadcn. Use for building any React component, reviewing component architecture, auditing accessibility and keyboard navigation, choosing between as/asChild, designing variant APIs with CVA, applying data-attribute-driven styling, classifying artifacts (primitive/component/block/pattern/template/utility), extending HTML types, and managing controlled/uncontrolled state. Use proactively when creating or reviewing React components, designing component APIs, building design systems, implementing keyboard navigation, adding ARIA support, structuring compound components, choosing element flexibility patterns, or applying Tailwind styling systems. Examples: - user: "Build an accessible dialog" → semantic HTML, focus trap, keyboard map, ARIA, asChild trigger - user: "Re

0
installs
▌
Jalco UI Registry · jal-co bundle
Create, review, and document jalco ui registry items with shadcn-style ergonomics, strong variants, and docs-to-registry alignment. Use for adding jalco ui components or blocks, updating registry.json, writing component docs, reviewing API and composition quality, or navigating the jalco-ui docs and registry structure. Use proactively when working in /Users/justin/Documents/Github/jalco-ui or when the user asks to create a component, improve variants, write docs, or audit registry readiness.

0
installs
▌
Jalco Shadcn Registry · jal-co bundle
Build and maintain the jalco ui shadcn-compatible registry. Use when creating or reviewing registry items, editing registry.json, choosing registry item types, configuring namespaced registries, planning authentication, adding docs metadata, or ensuring MCP/open-in-v0 compatibility.

0
installs
▌
Tailwind Design System · jal-co
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

0
installs
▌
Jalco Component Builder · jal-co
Build jalco ui components through a deliberate workflow: clarify requirements, judge scope and file boundaries, prefer strong default states and restrained variants, implement with shadcn-style ergonomics, and ship aligned docs. Use when the user asks to create a component, build a component, make a new UI component, add a registry component, create a docs component, add variants, refactor a component, or review public components, demos, or docs-facing UI.

0
installs
▌
Vercel Composition Patterns · jal-co bundle
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

0
installs
▌
Vercel React Best Practices · jal-co bundle
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

0
installs
▌
Jalco Writing Component Docs · jal-co
Write and review jalco ui component documentation with consistent structure, concise descriptions, realistic examples, and registry-aligned metadata. Use when creating new component docs, updating existing docs, reviewing doc quality, or syncing registry-backed component copy.

0
installs
▌
Herdr · jal-co
Control Herdr, a terminal multiplexer for coding agents. Use Herdr to inspect or control panes, tabs, workspaces, terminals, run commands, or start and monitor background processes like dev servers. Use for subagents when the user or another skill explicitly asks for or requires subagents. Requires HERDR_ENV=1.

0
installs
▌
Thesvg · jal-co
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG. Use when the user asks for a brand logo, company icon, framework mark, service icon, or any "icon/logo for X" where X is a real brand or cloud service. Returns ready-to-use CDN URLs or raw SVG markup.

0
installs
▌
Show Me · jal-co
Use when a visual explanation would clarify code changes, control flow, architecture, component structure, state transitions, or interface concepts.

0
installs
▌
UX Sound · jal-co bundle
Decide whether an interface element should make a sound, which kind, how loud, and where the audio comes from (synthesis, recording, or ElevenLabs generation). Use when adding sound to a UI, choosing between synthesizing and sampling, levelling sounds against each other, syncing audio to animation, or auditing an existing sound layer. Triggers on: ui sound, ux sound, sonic ux, audio feedback, micro feedback, earcon, auditory icon, notification sound, alert sound, hover sound, click sound, sound effect, sfx, should this have sound, too loud, sounds cheap, sound doesn't fire, elevenlabs, sound generation.

0
installs
▌
Plannotator · jal-co bundle
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided Reviews. Invoke when asked to use Plannotator for anything not covered by a more specific plannotator-* skill.

0
installs
▌
Plain Writing · jal-co bundle
Cut AI writing tells from prose. Use when drafting, editing, or reviewing any text a human will read — documentation, README files, blog posts, commit bodies, PR descriptions, release notes, emails, marketing copy, changelogs, or a rewrite request. Provides a banned-word list, empty-phrase list, and the sentence patterns that make writing sound machine-generated, each with the fix. Triggers on: write, draft, rewrite, edit, revise, polish, proofread, tighten, copy, prose, blog post, article, README, documentation, changelog, release notes, announcement, landing page copy, email, "make this sound human", "sounds like AI", "too wordy", AI tells, slop, tone, voice.

0
installs
▌
Tldraw Offline · jal-co
Operate the user's tldraw offline canvas app, including open .tldraw or .tldr files. Use whenever a task involves inspecting, editing, arranging, connecting, linting, or scripting a tldraw Desktop canvas.

0
installs
▌
Growth UX Audit · jal-co
Audit product UI and UX flows for revenue opportunities without disrupting the existing experience. Use when reviewing onboarding, activation, conversion, pricing, checkout, upgrade, expansion, retention, referral, or monetization flows; when asked how a product can increase conversion, revenue, ARPU, retention, or paid adoption with tasteful changes. Read-only: observes the current flow, ranks low-interruption experiments, and protects usability and trust. Triggers on: growth audit, growth engineering, conversion audit, monetization audit, revenue opportunities, improve conversion, increase upgrades, product-led growth, activation, retention, expansion, paywall, upgrade prompt.

0
installs
▌
Pr Screenshots · jal-co
Use when attaching screenshots, images, or videos to GitHub or Azure DevOps issues, pull requests, and comments, especially for before-and-after UI evidence.

0
installs
▌
Background Terminals · jal-co
Run and manage long-lived shell commands in background terminals. Use for dev servers, watchers, streaming builds, and other commands that should keep running while the agent continues working.

0
installs
▌
Preparing Pull Requests · jal-co
Use when preparing, opening, updating, or finalizing a pull request; when asked to create a PR, draft a PR description, push a change for review, attach PR screenshots, or make a branch ready for review. Also use before implementing UI changes intended for a PR so before screenshots are captured in time.

0
installs
▌
Exa · jal-co
Web search, content crawling, code context lookup, company research, and deep AI research via Exa. Use when the user needs to search the web, fetch page content from a URL, find code examples or documentation, research a company, or run a deep research report on a complex topic.

0
installs
▌
Git · jal-co
Git and GitHub CLI mastery for version control operations. Use proactively for commits, branches, PRs, rebases, conflict resolution, and git history management. Covers conventional commits, branching strategies, and GitHub workflows. Examples: - user: "Commit these changes" → stage files, create conventional commit - user: "Create a PR" → push branch, use gh pr create with proper template - user: "Rebase on main" → fetch, rebase, handle conflicts - user: "Fix merge conflict" → identify conflicts, resolve, complete merge - user: "Squash my commits" → interactive rebase guidance - user: "What's the git history?" → git log with appropriate flags

0
installs
▌
Remocn · jal-co bundle
Build Remotion videos with remocn — a shadcn registry of copy-paste animation components and timeline-driven UI primitives. Use when composing video scenes, adding text animations, transitions, backgrounds, UI blocks, brand/social cards, or full compositions in a Remotion project. Triggers include "remocn", "video component", "add animation", "text reveal", "scene transition", "product demo video", "remotion component", "typewriter", "terminal simulator", "glass code block", and the UI-primitive tier: "video dialog", "video button", "command menu", "video select", "video tooltip". Even if the user doesn't mention remocn, activate when they need polished video primitives for Remotion.

0
installs
▌
Repo CI · jal-co bundle
Set up GitHub repo CI with Husky git hooks, commit-check-action, conventional commits, and conventional branch naming. Handles greenfield and existing repos intelligently — detects existing CI, package managers, and config before making changes. Use when setting up CI, adding git hooks, enforcing commit conventions, or standardizing branch naming. Examples: - user: "Set up CI for this repo" → assess repo, install husky + commit-check - user: "Add conventional commits" → configure local hooks + GitHub Action - user: "Enforce branch naming" → add commit-check branch validation - user: "/setup-ci" → full CI pipeline setup with interactive questions - user: "Add husky to this project" → install and configure husky hooks

0
installs
▌
Grep App · jal-co bundle
Search for real-world code examples across a million GitHub repositories. Use when you need to find actual code patterns, library usage examples, or implementation patterns. Triggers include "search GitHub for", "find code examples of", "how do developers use", "show real-world usage of", or any need to see production code patterns.

0
installs
▌
Pi Skills · jal-co bundle
Create and manage pi skills with proper SKILL.md format, frontmatter, and organization. Use for skill creation, naming conventions, bundled resources (scripts/references/assets), progressive disclosure patterns, MCP-related skill documentation, and deciding when to use skills vs Pi MCP servers. Use proactively when user says "create a skill", "SKILL.md", "add a skill", "document this workflow", "add MCP server docs", or asks about skill structure.

0
installs
▌
Docs Writer · jal-co
Write, edit, review, and restructure Shieldcn documentation with accurate code-backed content, Fumadocs MDX conventions, and consistent technical-writing style. Use for docs rewrites, badge provider docs, API reference updates, sidebar/meta changes, documentation audits, and consolidation work. Triggers include "redo the docs", "write docs", "review docs", "update badge docs", "consolidate docs", "docs style", or any task modifying packages/web/content/docs.

0
installs
▌
Ship Or Skip · jal-co bundle
A realistic co-founder critic for software/product ideas. Use when the user wants an honest assessment of whether an idea is worth building, to find existing competitors, to size a niche, to pressure-test positioning, or to name a product and check domain availability. Triggers include "is this idea worth it", "ship or skip", "vet my idea", "who are the competitors", "is this niche too small", "is the competition too big", "name this product", "critique my startup idea", or sorting a backlog of ideas into pursue / refine / kill.

0
installs
▌
Browser Tools · jal-co bundle
Interactive browser automation via Chrome DevTools Protocol using Brave. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.

0
installs
▌
Rfc XML Style · jal-co bundle
RFC 2119 keywords and XML tag structure guide for agent prompts, skill definitions, and internal documentation. Use when writing, reviewing, or refactoring markdown files that instruct AI agents — including skills, prompt templates, system prompts, and workflow docs. Provides keyword semantics, XML tag catalog, nesting best practices, and before/after examples. Examples: - user: "Refactor this skill to use RFC keywords" → apply RFC 2119 keyword conventions - user: "Add XML structure to this prompt" → wrap sections in semantic XML tags - user: "Review my SKILL.md formatting" → audit RFC keyword usage and XML structure - user: "Convert this doc to RFC+XML style" → full transformation with style guide - user: "/refactor-rfc-xml ./prompts" → batch refactor all markdown in a folder

0
installs
▌
MCP Management · jal-co
Create, update, migrate, and debug MCP server configuration for Pi using pi-mcp-adapter. Use when adding an MCP server, editing ~/.pi/agent/mcp.json, importing MCP configs, switching from legacy MCPorter workflows, or documenting MCP setup. Use proactively when auth, server wiring, direct tools, or environment-variable based config is involved.

0
installs
▌
Security AI Keys · jal-co bundle
Review AI API key leakage patterns and redaction strategies. Use for identifying exposed keys for OpenAI, Anthropic, Gemini, and 10+ other providers. Use proactively when code integrates AI providers or when environment variables/keys are present. Examples: - user: "Check for leaked OpenAI keys" → scan for `sk-` patterns and client-side exposure - user: "Is my Gemini integration secure?" → audit vertex AI config and key redaction - user: "Review AI provider logging" → ensure secrets are redacted from logs - user: "Scan for Anthropic secrets" → check for `ant-` keys in code and configs - user: "Audit Vertex AI integration" → verify proper IAM roles and service account usage

0
installs
▌
Security Secrets · jal-co bundle
Review 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

0
installs
▌
Shadcn · jal-co
shadcn/ui component library patterns and usage. Use proactively when working with shadcn, Radix UI primitives, or building UI components with Tailwind CSS in React/Next.js projects. Examples: - user: "Add a dialog component" → shadcn add dialog, usage patterns - user: "Create a form with validation" → react-hook-form + zod + shadcn form - user: "Add a dropdown menu" → shadcn add dropdown-menu, composition patterns - user: "Style this button" → shadcn button variants, cva patterns - user: "Add a data table" → shadcn table + tanstack-table integration - user: "Create a command palette" → shadcn command (cmdk) setup - user: "Add dark mode" → next-themes + shadcn theming

0
installs
▌
Ink Tui · jal-co bundle
Build terminal UIs with Ink (React for CLIs). Use for interactive CLI apps, dashboards, menus, forms, progress indicators, and terminal-based interfaces. Use proactively when user says "build TUI", "terminal UI", "CLI interface", "ink component", "ink spinner", "ink select", "terminal dashboard", or mentions React-style terminal apps. Examples: - user: "Create an interactive CLI menu" → build with Ink + ink-select-input - user: "Add a progress bar to my CLI" → implement with ink-progress-bar or @inkjs/ui - user: "Build a terminal dashboard" → compose Box/Text with hooks and ecosystem components - user: "Make a multi-step wizard CLI" → ink-stepper or multi-screen pattern - user: "Add keyboard navigation to my CLI" → useInput, useFocus, useFocusManager

0
installs
▌
Opentui · jal-co bundle
Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.

0
installs
▌
Security Bun · jal-co bundle
Review 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

0
installs
▌
Agent Browser · jal-co bundle
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

0
installs
▌
MCP Installer · jal-co bundle
Find, install, and configure MCP servers. Use proactively for MCP discovery, OAuth setup, env vars, stdio vs SSE transport, or troubleshooting MCP connections. Examples: - user: "Add the filesystem MCP server" → read server file, add to mcpServers in opencode.json, verify transport type - user: "How do I use MCP with GitHub?" → check catalog, install @modelcontextprotocol/server-github, configure OAuth token - user: "MCP not connecting" → check transport type (stdio/SSE), verify args/command, check env vars are passed - user: "What MCPs are available?" → run list_mcps.py, show catalog with auth types and install commands

0
installs
▌
Security Vite · jal-co bundle
Review Vite security audit patterns for SPA and dev server security. Use for auditing VITE_* exposure, build-time secrets, and proxy configs. Use proactively when reviewing Vite apps (vite.config.ts present). Examples: - user: "Audit Vite env vars" → check for secrets with VITE_ prefix - user: "Check Vite build config" → verify define block and source maps - user: "Review Vite dev server" → check host binding and proxy security - user: "Scan Vite bundles" → search dist/ for leaked API keys or secrets - user: "Audit Vite SPA auth" → verify server-side auth vs client route guards

0
installs
▌
Opencode Agents · jal-co
Define and configure OpenCode agents with proper permissions, tools, and behaviors. Use for agent creation, tool access control, permission patterns, and mode selection. Use proactively when user says "create an agent", "agent permissions", "tool access", "subagent", "restrict agent", or asks about agent configuration. Examples: - user: "Create a security reviewer agent" → design agent with read-only permissions, appropriate skills - user: "How do I restrict bash access?" → explain permission.bash patterns with allow/ask/deny - user: "Make an agent use the question tool" → configure tools.question: "enabled" or ensure no tools restrictions - user: "What's the difference between primary and subagent?" → explain mode options

0
installs
▌
Opencode Config · jal-co bundle
Edit opencode.json, AGENTS.md, and config files. Use proactively for provider setup, permission changes, model config, formatter rules, or environment variables. Examples: - user: "Add Anthropic as a provider" → edit opencode.json providers, add API key baseEnv var, verify with opencode run test - user: "Restrict this agent's permissions" → add permission block to agent config, set deny/allow for tools/fileAccess - user: "Set GPT-5 as default model" → edit global or agent-level model preference, verify model name format - user: "Disable gofmt formatter" → edit formatters section, set languages.gofmt.enabled = false

0
installs
▌
Opencode Skills · jal-co
Create and manage OpenCode skills with proper SKILL.md format, frontmatter, and organization. Use for skill creation, naming conventions, permission configuration, and reference management. Use proactively when user says "create a skill", "SKILL.md", "skill discovery", "skill permissions", or asks about skill structure. Examples: - user: "Create a skill for database migrations" → design SKILL.md with description, instructions, optional references/ - user: "How do I restrict which skills an agent can use?" → explain permission.skill patterns - user: "Where should I put my skill?" → explain project vs global paths

0
installs
▌
Security Convex · jal-co bundle
Review Convex security audit patterns for authentication and authorization. Use for auditing query/mutation auth, row-level security, and validators. Use proactively when reviewing Convex apps (convex/ directory present). Examples: - user: "Audit these Convex mutations" → check for missing ctx.auth and input validators - user: "Check for IDOR in Convex queries" → verify ownership checks on document access - user: "Review Convex HTTP actions" → check for signature verification on webhooks - user: "Secure these Convex queries" → implement custom functions for enforced auth - user: "Check for data leaks in subscriptions" → verify filtered result sets

0
installs
▌
Security Django · jal-co bundle
Review 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

0
installs
▌
Security Docker · jal-co bundle
Review 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

0
installs
▌
Security Nextjs · jal-co bundle
Review Next.js security audit patterns for App Router and Server Actions. Use for auditing NEXT_PUBLIC_* exposure, Server Action auth, and middleware matchers. Use proactively when reviewing Next.js apps. Examples: - user: "Scan Next.js env vars" → find leaked secrets with NEXT_PUBLIC_ prefix - user: "Audit Server Actions" → check for missing auth and input validation - user: "Review Next.js middleware" → verify matcher coverage for protected routes - user: "Check Next.js API routes" → verify auth in app/api and pages/api - user: "Secure Next.js headers" → audit next.config.js for security headers

0
installs
▌
Model Researcher · jal-co bundle
Add new/custom AI models to opencode.json. Use proactively for bleeding-edge releases, non-standard providers, self-hosted models, or custom endpoints. Examples: - user: "Add the new Claude 4.5" → websearch for API specs, add provider entry with baseUrl, verify model ID format - user: "Use my local Ollama instance" → configure custom provider with http://localhost:11434, set model ID format - user: "Configure this OpenAI-compatible proxy" → add provider with custom baseUrl, set apikey env var, verify compatibility - user: "Model X just released, add it" → research provider documentation, find model ID and capabilities, add to config

0
installs
▌
Plugin Installer · jal-co bundle
Find, install, and configure OpenCode plugins from the catalog or community. Use proactively when user asks about plugins, requests new capabilities, or mentions extending OpenCode functionality. Examples: - user: "Is there a plugin for Tailwind CSS?" → list catalog, read tailwind plugin details, install if available - user: "How do I add a custom slash command?" → suggest command-creator skill or guide through opencode.json setup - user: "What plugins are available for database work?" → list catalog, filter for database-related plugins - user: "Install the playwright plugin" → read plugin file, add to opencode.json, verify installation

0
installs
▌
Security Express · jal-co bundle
Review Express.js security audit patterns for middleware and routes. Use for auditing Helmet.js, CORS, body-parser limits, and auth middleware. Use proactively when reviewing Express.js apps. Examples: - user: "Secure my Express app" → add Helmet.js and disable x-powered-by - user: "Check Express CORS config" → verify origin allowlists and credentials - user: "Review Express auth middleware" → check route order and coverage - user: "Scan for Express path traversal" → verify path normalization and validation - user: "Audit Express session config" → check secure, httpOnly, and sameSite flags

0
installs
▌
Security Fastapi · jal-co bundle
Review FastAPI security audit patterns for dependencies and middleware. Use for auditing auth dependencies, CORS configuration, and TrustedHost middleware. Use proactively when reviewing FastAPI apps. Examples: - user: "Audit FastAPI route security" → check for Depends() and Security() usage - user: "Check FastAPI CORS setup" → verify origins when allow_credentials=True - user: "Review FastAPI middleware" → check TrustedHost and HTTPSRedirect config - user: "Secure FastAPI API keys" → move from query params to header schemes - user: "Scan for FastAPI footguns" → check starlette integration and dependency order

0
installs
▌
Opencode Commands · jal-co
Create and manage OpenCode slash commands. Use for defining /command shortcuts, template syntax, argument interpolation, and workflow composition. Use proactively when user says "create a command", "slash command", "/command", "shortcut for", or asks about command frontmatter options. Examples: - user: "Create a /review command" → design command with description, optional agent routing - user: "How do I pass arguments to commands?" → explain $ARGUMENTS, $1, $2, `!shell`, @file - user: "Make a command that runs tests" → create command with shell interpolation

0
installs
▌
Opencode Improved · jal-co
Analyze external resources (GitHub repos, documentation, articles) and suggest improvements to OpenCode configuration. Use for discovering new patterns, comparing implementations, and enhancing existing skills, commands, and agents. Use proactively when user says "improve based on", "learn from", "compare to", "what can I learn from", or provides a link to analyze. Examples: - user: "What can I learn from this repo?" → analyze and suggest concrete improvements - user: "Improve my agents based on this article" → extract patterns, propose updates - user: "/improve https://github.com/example/config" → compare and recommend enhancements

0
installs
▌
User Onboarding Sop · jal-co
Generate AGENTS.md for end-user assistance. Covers setup, installation, running, and troubleshooting. This is for END-USER help, NOT developer/contributor docs. Use for /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

0
installs
▌
Agent Navigation Sop · jal-co
Generate AGENTS.md for AI agent navigation. Covers build/test commands, coding conventions, task routing, and codebase structure. Use for /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

0
installs
▌
Component Engineering · jal-co bundle
Apply 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

0
installs
▌
Vite Shadcn Tailwind4 · jal-co
Initialize 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

0
installs
▌
Create Opencode Plugin · jal-co bundle
Create OpenCode plugins using the @opencode-ai/plugin SDK. Use for building custom tools, event hooks, auth providers, or tool execution interception. Use proactively when developing new plugins in .opencode/plugin/ or ~/.config/opencode/plugin/. Examples: - user: "Create a plugin to block dangerous commands" → implement tool execution before hook with blocking logic - user: "Add a custom tool for jira" → design tool schema and implementation using SDK context - user: "Show toast on file edit" → react to file edit events and display status message - user: "Build a custom auth provider" → implement auth flow for new model provider - user: "Intercept git commits" → add hook to validate commit messages before execution

0
installs
▌
Shieldcn Badges · jal-co
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance. Triggers include "add badges", "add shields", "README badges", "npm badge", "GitHub stars badge", "CI badge", "download chart", "README header", "README banner", "contributors grid", "sponsors grid", "build a README", "README Studio", "shieldcn", and requests to make a project README look better.

1
install

62 published skills