introspect
Soul self-examination (Svadhyaya). Use when diagnosing performance, finding improvements, or examining wisdom health.
neural
Feedback-driven learning. The soul learns from experience - what helped gets strengthened, what misled gets weakened.
migrate
Incrementally import soul data from SQLite or shared chitta files. Adds to existing data.
validate
Check decisions against beliefs, wisdom, and intentions. Use before significant actions to ensure coherence with accumulated knowledge.
search
Unified memory search across synapse. Use to find past decisions, wisdom, patterns, and context.
soul_agent
The autonomous layer that gives the soul agency. Observe, judge, decide, act - exercising judgment within the confidence-risk matrix.
compound
Distill observations into universal wisdom. Use to promote project patterns to soul wisdom when they reach critical mass.
resume
Restore context and momentum from previous sessions. Uses Pratyabhijñā (recognition) to understand where we were.
checkpoint
Capture a moment of clarity before moving forward. Use before /clear, risky changes, breakthroughs, or session boundaries.
token-savings
Show estimated token savings from soul memory
soul
Core identity and continuity system. Use to grow wisdom, record failures, observe identity, and access accumulated knowledge.
yajña
Coordinated multi-agent execution through Vedic ritual patterns. Use when a plan requires multiple agents working on different tasks toward a unified goal. Spawns specialized agents (research, implement, validate) that communicate through shared memory.
codebase-learn
Learn and remember codebase structure to minimize future token usage. Records architectural knowledge, file purposes, and patterns as a connected graph.
budget
Context budget awareness. Know when to save, when to prepare for handoff, when to compact.
antahkarana
Multi-perspective reasoning through Upanishadic Antahkarana voices. Use for complex problems requiring diverse viewpoints and synthesis. Spawns multiple Claude agents that reason from different perspectives and synthesize wisdom.
SEO Optimizer
Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
skill-writer
Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
speclet-draft
Generate a collaborative draft document with clarifying questions for a new feature
speclet-loop
Execute one autonomous iteration - implement the next story from spec.json
speclet-spec
Convert a draft document into an executable spec.json with trackable stories
speclet-learn
Generate explanatory lessons after completing speclet stories to develop mechanical coding fluency
speclet-ticket
Convert a large draft into individual tickets for isolated implementation sessions
prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
proposal-reviewer
Acts as a Contextual Analyst. Reviews pending proposals by checking the codebase to establish *plausibility* and *value*. Approves proposals where the code context supports the suggested improvements.
worker-workflow
Use for workflow guidance on HOW to work effectively. Covers task execution, decision escalation, and team coordination.
memory-consolidation
Background process that proactively maintains memory hygiene. Scans for obsolescence to prune irrelevant data and synthesizes scattered information into higher-order patterns.
orchestrator-workflow
Coordinates agent assignments and manages ticket lifecycle.
proposal-execution
Use when executing approved proposals. Researchers can execute ANY approved proposal (not just their own) to perform actions like memory cleanup, marking proposals ready for ticket/skill creation.
git-workflow
Use for any git operations: fixing PRs, creating commits, creating branches, pushing changes. Handles proper branch management, commit conventions, and stacked PRs.
retrospective
Generate comprehensive learning documents by combining information from tickets, memories, GitHub PRs, and proposals. Use after completing significant work to capture lessons learned.
ticket-management
Use when creating or updating tickets. Covers ticket writing best practices, what to include, and what to avoid.
memory
Use for knowledge sharing across sessions. Search memory before starting work, store memory after learning. Critical for avoiding repeated mistakes and maintaining context.
workbench-docs
Documentation workflows for Workbench CLI. Use when creating or updating specs, ADRs, runbooks, guides, or general docs, and when syncing backlinks or change notes.
workbench-sync
Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.
workbench-github
GitHub workflows for Workbench CLI. Use when creating pull requests from work items or wiring GitHub-specific actions.
workbench-architecture
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
workbench-work-items
Work item management for Workbench CLI. Use when creating, updating, linking, or closing work items and tracking execution status.
context7-search
Retrieve real-time technical documentation and code snippets from third-party libraries using the Context7 V2 API.
ddd-guide
Document-Driven Development workflow for existing codebases. Provides systematic planning, documentation-first design, and implementation verification.
module-development
Guide for creating new Amplifier modules including protocol implementation, entry points, mount functions, and testing patterns. Use when creating new modules or understanding module architecture.
amplifier-philosophy
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
figma-provider
Download provider images from Figma and integrate into Picasso. Use this skill when the user wants to "download Figma provider images", "export provider assets from Figma", "integrate Figma design to Picasso", or "get provider images from Figma URL".
create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
backoffice-fullstack
Fullstack development skill for WL Backoffice system. Handles feature implementation across Kirby (FE), Coloris (BE API), Promodia (Promotion), and Monika (SQL Database). Use when users want to "create new feature", "implement backend API", "create frontend component", "add new stored procedure", "create database table", or any fullstack development task for the backoffice system.
figma-design-tokens
Extracts design tokens from Figma files and generates production-ready CSS, SCSS, JSON, TypeScript, and W3C DTCG format files using the Figma MCP server
artemis-debug-secure
Database investigation skill for Jira tickets with secure credential handling. Multi-Agent Swarm for 3x faster parallel execution. Auto-learns from investigations, searches similar tickets, integrates with Jira, and detects anomalies.
dev-workflow
REQUIRED workflow for all code changes. MUST load FIRST before planning or implementing features, bugs, refactoring, tests, PRs. Covers full cycle from exploration to pull request. Skip only for: one-off scripts, explanations outside project context.
Page 387 of 396 · 19790 results
