amhuppert/init-design-config
claude/ai-resources-plugin/skills/init-design-config/SKILL.md
Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
$ install --global
skillsauthnpx skillsauth add amhuppert/my-ai-resources init-design-configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:45 AM158.1s1 file scanned
SKILL.md
- name:
- init-design-config
- description:
- Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
- disable-model-invocation:
- true
- allowed-tools:
- Read, Grep, Glob, Write
Initialize a memory-bank/DESIGN-AGENTS.md configuration file for the /design workflow, populated with values discovered from project context.
Process
Step 1: Check if File Exists
Check if memory-bank/DESIGN-AGENTS.md already exists.
If it exists, report to user and ask if they want to overwrite or abort.
Step 2: Discover Project Context
Gather information from the project to populate the configuration:
Design System File:
- Search for design system files:
- Glob for
**/design-system*.md,**/design-spec*.md,**/*-design*.md - Check
docs/,agent-docs/,memory-bank/directories
- Glob for
- If found, use the path; otherwise use placeholder
[path/to/design-system.md - remove if none]
Requirements File:
- Search for requirements files:
- Glob for
memory-bank/*requirements*.md,memory-bank/*REQUIREMENTS*.md - Also check
docs/*requirements*.md,**/PRD*.md
- Glob for
- If found, use the path; otherwise use placeholder
[auto-detected from memory-bank/*requirements*.md]
Existing Project Agents:
- Check if
.claude/agents/directory exists - If it does, list any existing agents that might be design-related
- Note these for potential inclusion in Research/Review sections
Project Type (for suggestions):
- Check for
tsconfig.json→ suggest TypeScript-related agents - Check for
app.jsonwith expo → suggest mobile-related agents - Check
.kiro/steering/tech.mdfor domain hints
Step 3: Generate Configuration Content
Create the DESIGN-AGENTS.md content:
# Design Agents Configuration
This file configures project-specific agents for the `/design` workflow.
## Configuration
Optional settings for the design workflow:
- design-system-file: [discovered path or placeholder]
- requirements-file: [discovered path or placeholder]
## Research Agents
Domain experts that gather information during Phase 2 (before design synthesis).
These agents run in parallel to research specific aspects of the problem domain.
Add entries as: `- agent-name: Brief description of expertise`
[If domain hints found from steering files, add suggestions as comments:]
<!-- Suggested based on project context:
- [domain]-expert-agent: Researches [domain] best practices and patterns
-->
## Review Agents
Additional reviewers beyond the universal agents that run during Phase 4.
These agents evaluate the design draft for project-specific concerns.
Add entries as: `- agent-name: Brief description of what it reviews`
[If existing project agents found, list them as suggestions:]
<!-- Existing agents in .claude/agents/ that could be added:
- [agent-name]: [description if available]
-->
<!-- Common review agents to consider:
- security-review-agent: Reviews for authentication, authorization, and data protection
- performance-review-agent: Reviews for performance bottlenecks and optimization opportunities
- accessibility-review-agent: Reviews for WCAG compliance and inclusive design
-->
Step 4: Create Directory if Needed
If memory-bank/ directory doesn't exist, create it.
Step 5: Write the File
Write the generated content to memory-bank/DESIGN-AGENTS.md.
Step 6: Report Results
Report to the user:
## DESIGN-AGENTS.md Initialized
**Location**: memory-bank/DESIGN-AGENTS.md
### Discovered Values
- **Design System**: [path found | not found - placeholder added]
- **Requirements**: [path found | not found - will auto-detect]
### Next Steps
1. Review and update `memory-bank/DESIGN-AGENTS.md`
2. Remove placeholder comments for unused sections
3. Add project-specific research and review agents:
- Use `/add-design-agent` to create new agents
- Or manually add existing agents from `.claude/agents/`
4. Run `/design` to start the design workflow
### Universal Agents (always included)
The following agents run automatically for all projects:
- requirements-validation-agent
- software-engineering-agent
- simplicity-advocate-agent
- testing-strategy-agent
- ux-usability-agent
### Conditional Agents (auto-detected)
These agents are included based on project type:
[List which conditional agents will be included based on detection]
- [If TypeScript]: typescript-type-safety-agent ✓
- [If Expo]: expo-best-practices-agent ✓
- [If design system configured]: design-system-agent ✓
Related Skills
amhuppert/hotkey-helper
tools
VerifiedTrustedCommunity
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
2SKILL.mdUpdated Jun 2, 2026
amhuppert/knip
development
VerifiedTrustedCommunity
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
1SKILL.mdUpdated May 27, 2026
amhuppert/react-scan
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
1SKILL.mdUpdated May 20, 2026
amhuppert/knowledge-base-ingest
documentation
VerifiedTrustedCommunity
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".
1SKILL.mdUpdated May 17, 2026