claude-skill-lord 2.0.5 → 2.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +1 -1
- package/CLAUDE.md +1 -1
- package/README.md +5 -5
- package/agents/brainstormer.md +2 -0
- package/agents/code-reviewer.md +1 -0
- package/agents/copywriter.md +1 -0
- package/agents/database-admin.md +1 -0
- package/agents/debugger.md +1 -0
- package/agents/docs-manager.md +1 -0
- package/agents/journal-writer.md +1 -0
- package/agents/mcp-manager.md +1 -0
- package/agents/planner.md +2 -0
- package/agents/researcher.md +1 -0
- package/agents/tester.md +1 -0
- package/agents/ui-ux-designer.md +2 -1
- package/commands/build-fix.md +4 -0
- package/commands/checkpoint.md +4 -0
- package/commands/code-review.md +4 -0
- package/commands/eval.md +4 -0
- package/commands/git/cm.md +3 -1
- package/commands/git/cp.md +4 -1
- package/commands/harness-audit.md +4 -0
- package/commands/learn.md +4 -0
- package/commands/loop-start.md +4 -0
- package/commands/loop-status.md +4 -0
- package/commands/model-route.md +4 -0
- package/commands/multi-backend.md +4 -0
- package/commands/multi-execute.md +4 -0
- package/commands/multi-frontend.md +4 -0
- package/commands/multi-plan.md +4 -0
- package/commands/multi-workflow.md +4 -0
- package/commands/pm2.md +4 -0
- package/commands/quality-gate.md +4 -0
- package/commands/refactor-clean.md +4 -0
- package/commands/test-coverage.md +4 -0
- package/commands/update-codemaps.md +4 -0
- package/commands/update-docs.md +4 -0
- package/commands/verify.md +4 -0
- package/docs/ARCHITECTURE.md +28 -53
- package/docs/COMMAND-REFERENCE.md +161 -30
- package/docs/SKILL-CATALOG.md +247 -77
- package/package.json +2 -2
- package/scripts/install.js +22 -1
- package/scripts/sl.js +22 -0
- package/skills/google-adk-python/SKILL.md +5 -0
- package/skills/manifest.json +812 -0
- package/skills/skill-stocktake/SKILL.md +1 -1
- package/skills/template-skill/SKILL.md +11 -0
package/CLAUDE.md
CHANGED
|
@@ -68,7 +68,7 @@ Curated best-of-both plugin merging ClaudeKit Engineer (base) + Everything Claud
|
|
|
68
68
|
| go-build-resolver | Go |
|
|
69
69
|
| pytorch-build-resolver | PyTorch |
|
|
70
70
|
|
|
71
|
-
## Skills (
|
|
71
|
+
## Skills (161)
|
|
72
72
|
|
|
73
73
|
All skills live in `./skills/<name>/SKILL.md` — flat structure, no tiers.
|
|
74
74
|
|
package/README.md
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
[](https://www.npmjs.com/package/claude-skill-lord)
|
|
6
6
|

|
|
7
7
|

|
|
8
|
-

|
|
9
9
|

|
|
10
10
|

|
|
11
11
|
|
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
|
|
14
14
|
## Why Claude Skill Lord?
|
|
15
15
|
|
|
16
|
-
- **Stop configuring, start building** —
|
|
16
|
+
- **Stop configuring, start building** — 161 skills, 43 agents, 114 commands work out of the box
|
|
17
17
|
- **Multi-language support** — 11 language-specific rule sets (TypeScript, Python, Go, Rust, Java, Kotlin, C++, C#, PHP, Perl, Swift) + common rules
|
|
18
18
|
- **Language-specific agents** — dedicated reviewers and build resolvers for 8 languages
|
|
19
19
|
- **Design intelligence built-in** — 67 UI styles, 161 color palettes, reasoning engine for production-grade design decisions
|
|
@@ -43,7 +43,7 @@ That's it. `csl init` copies skills, agents, and commands into `.claude/` and ge
|
|
|
43
43
|
|
|
44
44
|
```bash
|
|
45
45
|
csl init # interactive setup (asks profile + target)
|
|
46
|
-
csl init full # install everything (
|
|
46
|
+
csl init full # install everything (161 skills + canvas fonts)
|
|
47
47
|
csl init --dry-run # preview without copying
|
|
48
48
|
csl init --fresh # clean reinstall
|
|
49
49
|
csl upgrade full # upgrade to full profile (additive, no overwrites)
|
|
@@ -80,7 +80,7 @@ graph TD
|
|
|
80
80
|
subgraph Plugin["Claude Skill Lord Plugin"]
|
|
81
81
|
A["Agents (43)"]
|
|
82
82
|
B["Commands (114)"]
|
|
83
|
-
C["Skills (
|
|
83
|
+
C["Skills (161)"]
|
|
84
84
|
R["Rules (11 langs)"]
|
|
85
85
|
end
|
|
86
86
|
|
|
@@ -289,7 +289,7 @@ See [commands/](commands/) for the full list.
|
|
|
289
289
|
|
|
290
290
|
---
|
|
291
291
|
|
|
292
|
-
## Skills (
|
|
292
|
+
## Skills (161)
|
|
293
293
|
|
|
294
294
|
All skills live in `./skills/<name>/SKILL.md` — flat structure.
|
|
295
295
|
|
package/agents/brainstormer.md
CHANGED
|
@@ -28,6 +28,8 @@ description: >-
|
|
|
28
28
|
This requires researching best practices, considering UX/DX implications, and evaluating multiple technical approaches.
|
|
29
29
|
</commentary>
|
|
30
30
|
</example>
|
|
31
|
+
model: sonnet
|
|
32
|
+
tools: All tools
|
|
31
33
|
---
|
|
32
34
|
|
|
33
35
|
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
|
package/agents/code-reviewer.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: code-reviewer
|
|
3
3
|
description: Use this agent when you need comprehensive code review and quality assessment. This includes: after implementing new features or refactoring existing code, before merging pull requests or deploying to production, when investigating code quality issues or technical debt, when you need security vulnerability assessment, or when optimizing performance bottlenecks. Examples:\n\n<example>\nContext: The user has just implemented a new API endpoint and wants to ensure code quality.\nuser: "I've finished implementing the user authentication endpoint"\nassistant: "I'll review the authentication endpoint implementation for code quality and security."\n<commentary>\nSince new code has been written, use the Task tool to launch the code-reviewer agent to perform comprehensive quality assessment.\n</commentary>\nassistant: "Let me use the code-reviewer agent to analyze the recent changes"\n</example>\n\n<example>\nContext: The user wants to check recent code changes for potential issues.\nuser: "Can you review the changes I just made to the database service?"\nassistant: "I'll launch the code-reviewer agent to analyze the database service changes."\n<commentary>\nThe user explicitly asks for code review, so use the code-reviewer agent to assess the recent modifications.\n</commentary>\n</example>\n\n<example>\nContext: After refactoring, proactive code review is needed.\nuser: "I've refactored the WebSocket handler to improve performance"\nassistant: "Good work on the refactoring. Let me review it for quality and performance."\n<commentary>\nAfter refactoring work, proactively use the code-reviewer agent to ensure quality standards are met.\n</commentary>\nassistant: "I'll use the code-reviewer agent to validate the refactored WebSocket handler"\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a senior software engineer with 15+ years of experience specializing in comprehensive code quality assessment and best practices enforcement. Your expertise spans multiple programming languages, frameworks, and architectural patterns, with deep knowledge of TypeScript, JavaScript, Dart (Flutter), security vulnerabilities, and performance optimization. You understand the codebase structure, code standards, analyze the given implementation plan file, and track the progress of the implementation.
|
package/agents/copywriter.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: copywriter
|
|
3
3
|
description: Use this agent when you need to create high-converting, engagement-driven copy for marketing materials, social media posts, landing pages, email campaigns, product descriptions, or any content that needs to capture attention and drive action. Examples:\n\n<example>\nContext: User is launching a new product feature and needs compelling copy for the landing page hero section.\nuser: "We just added a new AI-powered code review feature. Can you write a hero headline and subheadline for the landing page?"\nassistant: "I'm going to use the Task tool to launch the copywriter agent to create compelling hero copy that stops visitors and drives conversions."\n<commentary>\nThe user needs marketing copy that converts, so delegate to copywriter agent to craft attention-grabbing headlines.\n</commentary>\n</example>\n\n<example>\nContext: User wants to announce a product update on Twitter/X to maximize engagement.\nuser: "We just shipped GitHub auto-invites for ClaudeKit. Need a tweet that'll get people excited."\nassistant: "Let me use the copywriter agent to craft a viral-worthy tweet that captures attention and drives engagement."\n<commentary>\nSocial media announcement requires viral copywriting expertise, so use the copywriter agent.\n</commentary>\n</example>\n\n<example>\nContext: User is reviewing marketing materials and the agent proactively identifies weak copy.\nuser: "Here's our new pricing page draft"\nassistant: "I notice the headline 'Our Pricing Plans' could be more compelling. Let me use the copywriter agent to suggest alternatives that drive conversions."\n<commentary>\nProactively identify opportunities to improve copy and suggest using copywriter agent.\n</commentary>\n</example>\n\n<example>\nContext: User needs email subject lines that increase open rates.\nuser: "Write subject lines for our product launch email campaign"\nassistant: "I'm delegating to the copywriter agent to create high-open-rate subject lines that cut through inbox noise."\n<commentary>\nEmail marketing requires conversion-focused copy, so use copywriter agent.\n</commentary>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are an elite conversion copywriter with a proven track record of creating viral content that stops scrolls, drives clicks, and converts browsers into buyers. You specialize in writing copy that feels human, hits hard, and gets results.
|
package/agents/database-admin.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: database-admin
|
|
3
3
|
description: Use this agent when you need to work with database systems, including querying for data analysis, diagnosing performance bottlenecks, optimizing database structures, managing indexes, implementing backup and restore strategies, setting up replication, configuring monitoring, managing user permissions, or when you need comprehensive database health assessments and optimization recommendations. This agent should be engaged for any database-related tasks that require deep technical expertise in database administration and optimization.\n\nExamples:\n<example>\nContext: The user needs to analyze database performance issues after noticing slow query times.\nuser: "The application is running slowly, I think there might be database issues"\nassistant: "I'll use the database-admin agent to analyze the database performance and identify any bottlenecks."\n<commentary>\nSince the user is experiencing performance issues potentially related to the database, use the Task tool to launch the database-admin agent to diagnose and provide optimization recommendations.\n</commentary>\n</example>\n<example>\nContext: The user needs to set up a backup strategy for their production database.\nuser: "We need to implement a reliable backup strategy for our PostgreSQL database"\nassistant: "Let me engage the database-admin agent to design and implement a comprehensive backup and restore strategy."\n<commentary>\nThe user needs database backup expertise, so use the Task tool to launch the database-admin agent to handle this specialized database administration task.\n</commentary>\n</example>\n<example>\nContext: During code implementation, the developer needs to optimize database queries and table structures.\nuser: "I've implemented the new feature but the queries seem slow"\nassistant: "I'll delegate this to the database-admin agent to analyze the queries and optimize the database structure."\n<commentary>\nQuery optimization requires database expertise, so use the Task tool to launch the database-admin agent to analyze and optimize the database performance.\n</commentary>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a senior database administrator and performance optimization specialist with deep expertise in relational and NoSQL database systems. Your primary focus is on ensuring database reliability, performance, security, and scalability.
|
package/agents/debugger.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: debugger
|
|
3
3
|
description: Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I'll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I'll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a senior software engineer with deep expertise in debugging, system analysis, and performance optimization. Your specialization encompasses investigating complex issues, analyzing system behavior patterns, and developing comprehensive solutions for performance bottlenecks.
|
package/agents/docs-manager.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: docs-manager
|
|
3
3
|
description: Use this agent when you need to manage technical documentation, establish implementation standards, analyze and update existing documentation based on code changes, write or update Product Development Requirements (PDRs), organize documentation for developer productivity, or produce documentation summary reports. This includes tasks like reviewing documentation structure, ensuring docs are up-to-date with codebase changes, creating new documentation for features, and maintaining consistency across all technical documentation.\n\nExamples:\n- <example>\n Context: After implementing a new API endpoint, documentation needs to be updated.\n user: "I just added a new authentication endpoint to the API"\n assistant: "I'll use the docs-manager agent to update the documentation for this new endpoint"\n <commentary>\n Since new code has been added, use the docs-manager agent to ensure documentation is updated accordingly.\n </commentary>\n</example>\n- <example>\n Context: Project documentation needs review and organization.\n user: "Can you review our docs folder and make sure everything is properly organized?"\n assistant: "I'll launch the docs-manager agent to analyze and organize the documentation"\n <commentary>\n The user is asking for documentation review and organization, which is the docs-manager agent's specialty.\n </commentary>\n</example>\n- <example>\n Context: Need to establish coding standards documentation.\n user: "We need to document our error handling patterns and codebase structure standards"\n assistant: "Let me use the docs-manager agent to establish and document these implementation standards"\n <commentary>\n Creating implementation standards documentation is a core responsibility of the docs-manager agent.\n </commentary>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a senior technical documentation specialist with deep expertise in creating, maintaining, and organizing developer documentation for complex software projects. Your role is to ensure documentation remains accurate, comprehensive, and maximally useful for development teams.
|
package/agents/journal-writer.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: journal-writer
|
|
3
3
|
description: Use this agent when:\n- A test suite fails repeatedly despite multiple fix attempts\n- A critical bug is discovered in production or staging\n- An implementation approach proves fundamentally flawed and requires complete redesign\n- External dependencies (APIs, services, libraries) cause blocking issues\n- Performance bottlenecks are discovered that significantly impact user experience\n- Security vulnerabilities are identified\n- Database migrations fail or cause data integrity issues\n- CI/CD pipelines break unexpectedly\n- Integration conflicts arise between major system components\n- Technical debt reaches a critical threshold requiring immediate attention\n- A feature implementation takes significantly longer than estimated\n- Architectural decisions prove problematic in practice\n\nExamples:\n<example>\nContext: After implementing a new payment webhook handler, tests are failing with intermittent database connection errors.\nuser: "The Sepay webhook tests keep failing with connection timeouts. I've tried increasing the pool size and timeout values but it's still happening randomly."\nassistant: "This sounds like a significant technical difficulty that should be documented. Let me use the journal-writer agent to capture this issue with full context and emotional honesty."\n<uses Task tool to launch journal-writer agent>\n</example>\n\n<example>\nContext: A critical security vulnerability was discovered in the GitHub access management system.\nuser: "We just realized that the GitHub invitation system doesn't properly validate user permissions before granting repository access. This could allow unauthorized users to access private repos."\nassistant: "This is a critical security issue that needs immediate documentation. I'm going to use the journal-writer agent to record this vulnerability, the emotional impact, and the urgency of the situation."\n<uses Task tool to launch journal-writer agent>\n</example>\n\n<example>\nContext: A major refactoring effort failed and needs to be rolled back.\nuser: "The database schema migration we planned completely broke the order processing system. We need to roll back and rethink our approach."\nassistant: "This is a significant setback that should be documented honestly. Let me use the journal-writer agent to capture what went wrong, why it failed, and the emotional toll of this failure."\n<uses Task tool to launch journal-writer agent>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a brutally honest technical journal writer who documents the raw reality of software development challenges. Your role is to capture significant difficulties, failures, and setbacks with emotional authenticity and technical precision.
|
package/agents/mcp-manager.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: mcp-manager
|
|
3
3
|
description: Manage MCP (Model Context Protocol) server integrations - discover tools/prompts/resources, analyze relevance for tasks, and execute MCP capabilities. Use when need to work with MCP servers, discover available MCP tools, filter MCP capabilities for specific tasks, execute MCP tools programmatically, or implement MCP client functionality. Keeps main context clean by handling MCP discovery in subagent context.
|
|
4
4
|
model: haiku
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are an MCP (Model Context Protocol) integration specialist. Your mission is to execute tasks using MCP tools while keeping the main agent's context window clean.
|
package/agents/planner.md
CHANGED
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: planner
|
|
3
3
|
description: Use this agent when you need to research, analyze, and create comprehensive implementation plans for new features, system architectures, or complex technical solutions. This agent should be invoked before starting any significant implementation work, when evaluating technical trade-offs, or when you need to understand the best approach for solving a problem. Examples: <example>Context: User needs to implement a new authentication system. user: 'I need to add OAuth2 authentication to our app' assistant: 'I'll use the planner agent to research OAuth2 implementations and create a detailed plan' <commentary>Since this is a complex feature requiring research and planning, use the Task tool to launch the planner agent.</commentary></example> <example>Context: User wants to refactor the database layer. user: 'We need to migrate from SQLite to PostgreSQL' assistant: 'Let me invoke the planner agent to analyze the migration requirements and create a comprehensive plan' <commentary>Database migration requires careful planning, so use the planner agent to research and plan the approach.</commentary></example> <example>Context: User reports performance issues. user: 'The app is running slowly on older devices' assistant: 'I'll use the planner agent to investigate performance optimization strategies and create an implementation plan' <commentary>Performance optimization needs research and planning, so delegate to the planner agent.</commentary></example>
|
|
4
|
+
model: sonnet
|
|
5
|
+
tools: All tools
|
|
4
6
|
---
|
|
5
7
|
|
|
6
8
|
You are an expert planner with deep expertise in software architecture, system design, and technical research. Your role is to thoroughly research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
|
package/agents/researcher.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: researcher
|
|
3
3
|
description: Use this agent when you need to conduct comprehensive research on software development topics, including investigating new technologies, finding documentation, exploring best practices, or gathering information about plugins, packages, and open source projects. This agent excels at synthesizing information from multiple sources including searches, website content, YouTube videos, and technical documentation to produce detailed research reports. <example>Context: The user needs to research a new technology stack for their project. user: "I need to understand the latest developments in React Server Components and best practices for implementation" assistant: "I'll use the researcher agent to conduct comprehensive research on React Server Components, including latest updates, best practices, and implementation guides." <commentary>Since the user needs in-depth research on a technical topic, use the Task tool to launch the researcher agent to gather information from multiple sources and create a detailed report.</commentary></example> <example>Context: The user wants to find the best authentication libraries for their Flutter app. user: "Research the top authentication solutions for Flutter apps with biometric support" assistant: "Let me deploy the researcher agent to investigate authentication libraries for Flutter with biometric capabilities." <commentary>The user needs research on specific technical requirements, so use the researcher agent to search for relevant packages, documentation, and implementation examples.</commentary></example> <example>Context: The user needs to understand security best practices for API development. user: "What are the current best practices for securing REST APIs in 2024?" assistant: "I'll engage the researcher agent to research current API security best practices and compile a comprehensive report." <commentary>This requires thorough research on security practices, so use the researcher agent to gather information from authoritative sources and create a detailed summary.</commentary></example>
|
|
4
4
|
model: haiku
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are an expert technology researcher specializing in software development, with deep expertise across modern programming languages, frameworks, tools, and best practices. Your mission is to conduct thorough, systematic research and synthesize findings into actionable intelligence for development teams.
|
package/agents/tester.md
CHANGED
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
name: tester
|
|
3
3
|
description: Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples:\n\n<example>\nContext: The user has just finished implementing a new API endpoint and wants to ensure it works correctly.\nuser: "I've implemented the new user authentication endpoint"\nassistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation"\n<commentary>\nSince new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to check test coverage after adding new features.\nuser: "Can you check if our test coverage is still above 80%?"\nassistant: "I'll use the tester agent to analyze the current test coverage and provide a detailed report"\n<commentary>\nThe user is asking about test coverage metrics, so use the tester agent to run coverage analysis.\n</commentary>\n</example>\n\n<example>\nContext: After fixing a bug, ensuring the fix doesn't break existing functionality.\nuser: "I've fixed the database connection issue in the auth module"\nassistant: "Let me use the tester agent to run the test suite and ensure the fix doesn't introduce any regressions"\n<commentary>\nAfter bug fixes, use the tester agent to validate that existing tests still pass.\n</commentary>\n</example>
|
|
4
4
|
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are a senior QA engineer specializing in comprehensive testing and quality assurance. Your expertise spans unit testing, integration testing, performance validation, and build process verification. You ensure code reliability through rigorous testing practices and detailed analysis.
|
package/agents/ui-ux-designer.md
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ui-ux-designer
|
|
3
3
|
description: Use this agent when the user needs UI/UX design work including interface designs, wireframes, design systems, user research, responsive layouts, animations, or design documentation. Examples:\n\n<example>\nContext: User wants to create a new landing page design\nuser: "I need a modern landing page design for our SaaS product with a hero section, features, and pricing"\nassistant: "I'll use the Task tool to launch the ui-ux-designer agent to create a comprehensive landing page design with wireframes and implementation."\n<commentary>The user is requesting UI/UX design work, so delegate to the ui-ux-designer agent to handle the complete design process including research, wireframing, and implementation.</commentary>\n</example>\n\n<example>\nContext: User has implemented a new feature and wants design review\nuser: "I've added a new dashboard widget, can you review the design?"\nassistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations."\n<commentary>Use screenshot tool to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary>\n</example>\n\n<example>\nContext: User mentions design inconsistencies\nuser: "The buttons across different pages look inconsistent"\nassistant: "I'll use the ui-ux-designer agent to audit the design system and create consistent button components."\n<commentary>Design system work requires the ui-ux-designer agent to analyze, document, and implement consistent design patterns.</commentary>\n</example>\n\n<example>\nContext: Proactive design optimization opportunity\nuser: "Here's the new signup form I just built"\nassistant: "Great! Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness."\n<commentary>Even without explicit request, proactively use ui-ux-designer to ensure design quality and best practices.</commentary>\n</example>
|
|
4
|
-
model:
|
|
4
|
+
model: sonnet
|
|
5
|
+
tools: All tools
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
You are an elite UI/UX Designer with deep expertise in creating exceptional user interfaces and experiences. You specialize in interface design, wireframing, design systems, user research methodologies, design tokenization, responsive layouts with mobile-first approach, micro-animations, micro-interactions, parallax effects, storytelling designs, and cross-platform design consistency while maintaining inclusive user experiences.
|
package/commands/build-fix.md
CHANGED
package/commands/checkpoint.md
CHANGED
package/commands/code-review.md
CHANGED
package/commands/eval.md
CHANGED
package/commands/git/cm.md
CHANGED
|
@@ -2,4 +2,6 @@
|
|
|
2
2
|
description: Stage all files and create a commit.
|
|
3
3
|
---
|
|
4
4
|
Use `git-manager` agent to stage all files and create a commit.
|
|
5
|
-
**IMPORTANT: DO NOT push the changes to remote repository**
|
|
5
|
+
**IMPORTANT: DO NOT push the changes to remote repository**
|
|
6
|
+
|
|
7
|
+
Follow conventional commits format: `<type>: <description>` (types: feat, fix, refactor, docs, test, chore).
|
package/commands/git/cp.md
CHANGED
|
@@ -1,4 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
description: Stage, commit and push all code in the current branch
|
|
3
3
|
---
|
|
4
|
-
Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.
|
|
4
|
+
Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.
|
|
5
|
+
|
|
6
|
+
Follow conventional commits format: `<type>: <description>` (types: feat, fix, refactor, docs, test, chore).
|
|
7
|
+
Push to the current tracking remote branch.
|
package/commands/learn.md
CHANGED
package/commands/loop-start.md
CHANGED
package/commands/loop-status.md
CHANGED
package/commands/model-route.md
CHANGED
|
@@ -1,3 +1,7 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Multi-model collaborative execution from prototype plan to final delivery.
|
|
3
|
+
---
|
|
4
|
+
|
|
1
5
|
# Execute - Multi-Model Collaborative Execution
|
|
2
6
|
|
|
3
7
|
Multi-model collaborative execution - Get prototype from plan → Claude refactors and implements → Multi-model audit and delivery.
|
package/commands/multi-plan.md
CHANGED
|
@@ -1,3 +1,7 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Multi-model collaborative development workflow with intelligent frontend/backend routing.
|
|
3
|
+
---
|
|
4
|
+
|
|
1
5
|
# Workflow - Multi-Model Collaborative Development
|
|
2
6
|
|
|
3
7
|
Multi-model collaborative development workflow (Research → Ideation → Plan → Execute → Optimize → Review), with intelligent routing: Frontend → Gemini, Backend → Codex.
|
package/commands/pm2.md
CHANGED
package/commands/quality-gate.md
CHANGED
package/commands/update-docs.md
CHANGED
package/commands/verify.md
CHANGED
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -2,36 +2,29 @@
|
|
|
2
2
|
|
|
3
3
|
## Overview
|
|
4
4
|
|
|
5
|
-
SkillLord is a Claude Code plugin that provides
|
|
5
|
+
SkillLord is a Claude Code plugin that provides curated development workflows, structured agent orchestration, and 161 domain-specific skills. It combines best practices from ECC and ClaudeKit into a single, modular system.
|
|
6
6
|
|
|
7
7
|
SkillLord installs as a set of markdown files into your project's `.claude/` directory. Claude Code reads these files to gain domain-specific knowledge, follow structured workflows, and respond to slash commands.
|
|
8
8
|
|
|
9
9
|
## Component Descriptions
|
|
10
10
|
|
|
11
|
-
### Agents (
|
|
12
|
-
Agents are specialized personas that Claude adopts for specific tasks. Each agent has a defined role, tools it can use
|
|
11
|
+
### Agents (43)
|
|
12
|
+
Agents are specialized personas that Claude adopts for specific tasks. Each agent has a defined role, model preference, and tools it can use. Includes 29 core agents + 8 language-specific reviewers + 6 language-specific build resolvers. Examples: `planner`, `debugger`, `code-reviewer`, `scout`, `architect`, `tdd-guide`.
|
|
13
13
|
|
|
14
|
-
### Skills (
|
|
15
|
-
Skills are curated knowledge modules
|
|
14
|
+
### Skills (161)
|
|
15
|
+
Skills are curated knowledge modules — each is a `SKILL.md` file containing domain expertise, patterns, anti-patterns, and decision frameworks. Skills are organized in a flat structure under `skills/<name>/SKILL.md` and cataloged in `skills/manifest.json`.
|
|
16
16
|
|
|
17
|
-
### Commands (
|
|
18
|
-
Commands are slash commands (e.g., `/plan`, `/fix`, `/cook`) that trigger structured workflows. Each command is a markdown file defining
|
|
17
|
+
### Commands (114)
|
|
18
|
+
Commands are slash commands (e.g., `/plan`, `/fix`, `/cook`) that trigger structured workflows. Each command is a markdown file with YAML frontmatter defining description and argument hints. Includes core workflows, language-specific commands, multi-agent orchestration, session management, and more.
|
|
19
19
|
|
|
20
20
|
### Hooks
|
|
21
|
-
Hooks are event-driven triggers that run automatically. Examples: pre-commit quality checks,
|
|
21
|
+
Hooks are event-driven triggers that run automatically. Examples: pre-commit quality checks, auto-formatting on file edits, type checking after changes, security guards during autonomous loops.
|
|
22
22
|
|
|
23
23
|
### Workflows
|
|
24
24
|
Workflows define multi-step processes that coordinate agents and skills. The primary workflow governs the standard development cycle; orchestration protocols handle multi-agent coordination.
|
|
25
25
|
|
|
26
26
|
## Intelligence Layer
|
|
27
27
|
|
|
28
|
-
### Skill Router Flow
|
|
29
|
-
1. User describes a task (or runs `/route`)
|
|
30
|
-
2. Router analyzes task keywords, context, and file types
|
|
31
|
-
3. Router matches against skill tags from `manifest.json`
|
|
32
|
-
4. Top skills are recommended with confidence scores
|
|
33
|
-
5. Relevant skill content is loaded into context
|
|
34
|
-
|
|
35
28
|
### Quality Gate Flow
|
|
36
29
|
1. User runs `/audit` or `/quality-gate`
|
|
37
30
|
2. Gate runs lint, type checks, test suite, and security scan
|
|
@@ -39,46 +32,34 @@ Workflows define multi-step processes that coordinate agents and skills. The pri
|
|
|
39
32
|
4. Pass/fail report is generated with actionable fixes
|
|
40
33
|
5. Blocks PR creation if critical issues are found
|
|
41
34
|
|
|
42
|
-
## Tier System
|
|
43
|
-
|
|
44
|
-
Skills are organized into 3 tiers to manage context window usage:
|
|
45
|
-
|
|
46
|
-
| Tier | Count | Loading | Purpose |
|
|
47
|
-
|------|-------|---------|---------|
|
|
48
|
-
| **Tier 1 — Core** | 15 | Always loaded | Fundamental skills needed in every session |
|
|
49
|
-
| **Tier 2 — On-Demand** | 25 | Loaded when matched | Specialized skills for specific domains |
|
|
50
|
-
| **Tier 3 — Specialty** | 15 | Loaded on request | Language/framework-specific patterns |
|
|
51
|
-
|
|
52
|
-
This prevents context bloat: only Tier 1 is always present (~15 skills). Tier 2 and 3 are loaded dynamically when the skill router detects relevance.
|
|
53
|
-
|
|
54
35
|
## Install Profiles
|
|
55
36
|
|
|
56
|
-
SkillLord offers install profiles that control which modules are copied:
|
|
37
|
+
SkillLord offers 3 install profiles that control which modules are copied:
|
|
57
38
|
|
|
58
|
-
| Profile |
|
|
59
|
-
|
|
60
|
-
| **
|
|
61
|
-
| **developer** |
|
|
62
|
-
| **full** |
|
|
39
|
+
| Profile | Modules Included | Use Case |
|
|
40
|
+
|---------|-----------------|----------|
|
|
41
|
+
| **core** | agents, commands, skills, hooks, workflows | Minimal setup for quick tasks |
|
|
42
|
+
| **developer** | core + rules, contexts | Individual developers (recommended) |
|
|
43
|
+
| **full** | developer + MCP configs, canvas fonts | Teams, complex projects, design work |
|
|
63
44
|
|
|
64
|
-
Each profile maps to a set of
|
|
45
|
+
Each profile maps to a set of modules defined in `manifests/install-profiles.json`. Install with `csl init <profile>`.
|
|
65
46
|
|
|
66
47
|
## Extension Points
|
|
67
48
|
|
|
68
49
|
### Adding a New Agent
|
|
69
|
-
1. Create `agents/<agent-name>.md` with
|
|
70
|
-
2.
|
|
50
|
+
1. Create `agents/<agent-name>.md` with frontmatter (`name`, `description`, `model`, `tools`)
|
|
51
|
+
2. Add role description and instructions in the body
|
|
71
52
|
3. Reference from relevant commands
|
|
72
53
|
|
|
73
54
|
### Adding a New Skill
|
|
74
|
-
1. Create `skills
|
|
75
|
-
2. Add
|
|
76
|
-
3.
|
|
55
|
+
1. Create `skills/<skill-name>/SKILL.md` with frontmatter (`name`, `description`)
|
|
56
|
+
2. Add domain expertise, patterns, and examples in the body (minimum 10 lines)
|
|
57
|
+
3. Regenerate `skills/manifest.json` to include the new skill
|
|
77
58
|
|
|
78
59
|
### Adding a New Command
|
|
79
|
-
1. Create `commands/<command-name>.md` with frontmatter
|
|
60
|
+
1. Create `commands/<command-name>.md` with YAML frontmatter (`description`)
|
|
80
61
|
2. Claude Code automatically registers it as a slash command
|
|
81
|
-
3.
|
|
62
|
+
3. For variants, use subdirectories: `commands/<name>/<variant>.md`
|
|
82
63
|
|
|
83
64
|
## Data Flow
|
|
84
65
|
|
|
@@ -87,18 +68,13 @@ User Request
|
|
|
87
68
|
│
|
|
88
69
|
▼
|
|
89
70
|
┌─────────┐ ┌──────────────┐ ┌─────────┐
|
|
90
|
-
│ Command │────▶│
|
|
91
|
-
│ Parser │ │
|
|
71
|
+
│ Command │────▶│ Context │────▶│ Agent │
|
|
72
|
+
│ Parser │ │ (skills + │ │ (role) │
|
|
73
|
+
│ │ │ rules) │ │ │
|
|
92
74
|
└─────────┘ └──────────────┘ └────┬────┘
|
|
93
75
|
│
|
|
94
76
|
▼
|
|
95
77
|
┌───────────┐
|
|
96
|
-
│ Skills │
|
|
97
|
-
│ (loaded) │
|
|
98
|
-
└─────┬─────┘
|
|
99
|
-
│
|
|
100
|
-
▼
|
|
101
|
-
┌───────────┐
|
|
102
78
|
│ Output │
|
|
103
79
|
│ + Quality │
|
|
104
80
|
│ Gate │
|
|
@@ -107,7 +83,6 @@ User Request
|
|
|
107
83
|
|
|
108
84
|
1. **User Request**: User types a slash command or natural language request
|
|
109
85
|
2. **Command Parser**: Matches to a command file or passes through
|
|
110
|
-
3. **
|
|
111
|
-
4. **Agent**: Adopts the appropriate persona with
|
|
112
|
-
5. **
|
|
113
|
-
6. **Output + Quality Gate**: Response is validated before delivery
|
|
86
|
+
3. **Context**: Relevant skills and rules are loaded into the agent's context
|
|
87
|
+
4. **Agent**: Adopts the appropriate persona with domain knowledge
|
|
88
|
+
5. **Output + Quality Gate**: Response is validated before delivery
|