monkilabs/project-consistency
src/orchestrator/skills/project-consistency/SKILL.md
Generates shared CSS variables, validates component naming conventions, creates layout pattern templates. Use when coordinating design system, theme, consistent styling, CSS variables, or component library across parallel agents.
$ install --global
skillsauthnpx skillsauth add monkilabs/opencastle project-consistencyInstall 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 19, 2026, 7:30 AM256.9s2 files scanned
SKILL.md
- name:
- project-consistency
- description:
- Generates shared CSS variables, validates component naming conventions, creates layout pattern templates. Use when coordinating design system, theme, consistent styling, CSS variables, or component library across parallel agents.
Project Consistency
Ensure consistency by producing shared artifacts, automated checks before parallel work begins.
Foundation-First Principle
Phase 1 (sequential): create shared artifacts (tokens, Layout, UI components). Phase 2 (parallel): every page imports from Phase 1; no new tokens or duplicated components.
Foundation Artifacts & Page Rules
| Artifact | Path | Page Agent Rules |
|----------|------|------------------|
| Design tokens | src/styles/tokens.css | Import only. Never introduce new color/font/spacing values. |
| Shared layout | src/components/Layout.tsx / Layout.astro | Wrap every page. Never recreate. |
| UI components | src/components/ui/ | Import from library. PascalCase components, camelCase props. |
| Style guide brief | Inline in prompts | Match tone + terminology exactly. Follow heading hierarchy. |
Validation checkpoints:
- Foundation complete:
tokens.csshas all palette/type/spacing vars, Layout renders, UI components compile. - Per-page:
grep -r .style={{. src/pages/returns 0 hits (no inline styles). All imports resolve.
Convoy Integration
Phase 1 (sequential): foundation-setup creates tokens, Layout, UI library, style guide brief. Phase 2 (parallel): every page task imports from Phase 1. Include these 5 references in every page prompt:
1. Design tokens path 2. Layout path 3. UI components path
4. Aesthetic direction 5. Content tone
Prompt templates: see TEMPLATES.md.
Executable Examples
Example: src/styles/tokens.css
:root {
/* Palette */
--color-bg: #ffffff;
--color-foreground: #0f172a;
--color-primary: #0ea5e9;
--color-primary-600: #0284c7;
/* Typography */
--font-base: 'Inter, system-ui, -apple-system, sans-serif';
--text-sm: 0.875rem;
--text-base: 1rem;
/* Spacing */
--space-1: 4px;
--space-2: 8px;
--space-3: 16px;
/* Radius */
--radius-sm: 6px;
--radius-md: 12px;
}
Minimal Button component example (React)
import './tokens.css';
type ButtonProps = { children: React.ReactNode; variant?: 'primary' | 'ghost'; className?: string };
export function Button({ children, variant = 'primary', className = '' }: ButtonProps) {
const base = 'px-4 py-2 rounded';
const variantCls = variant === 'primary' ? 'bg-[var(--color-primary)] text-white' : 'bg-transparent';
return <button className={`${base} ${variantCls} ${className}`}>{children}</button>;
}
Anti-Patterns
| Anti-pattern | Fix |
|-------------|-----|
| Agents pick their own fonts/colors | Foundation creates tokens first |
| Copy-pasting Button between pages | Import from shared library |
| Inline style={{ color: '#...' }} | CSS class with token variable |
| Foundation and page tasks run in parallel | Foundation phase must fully complete first |
Related Skills
monkilabs/validation-gates
development
VerifiedTrustedCommunity
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/testing-workflow
development
VerifiedTrustedCommunity
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/team-lead-reference
development
VerifiedTrustedCommunity
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/session-checkpoints
testing
VerifiedTrustedCommunity
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
44SKILL.mdUpdated Apr 21, 2026