Aurelius
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Uyari
- fs module — File system access in .github/workflows/ci.yml
Permissions Gecti
- Permissions — No dangerous permissions requested
This is a Claude Code-integrated framework designed to automate the full lifecycle of React application development. It features a specialized pipeline that converts Figma or Canva designs directly into fully tested React code using an array of AI agents.
Security Assessment
The overall security risk is Low. The tool does not request inherently dangerous permissions. However, it does rely heavily on shell scripts for automation (like initializing projects, running tests, and visual diffs). File system access is present within the CI workflows, which is standard for build and testing pipelines. Users should be aware that autonomous AI pipelines executing shell commands inherently run the instructions generated by the AI, so human oversight of the generated code is advised. No hardcoded secrets were detected.
Quality Assessment
The project is fresh, with repository activity as recent as today, and is properly licensed under the permissive MIT license. Despite being a highly capable and well-structured framework, community visibility is currently very low with only 5 GitHub stars. Because of its low visibility and lack of widespread community testing, the long-term maintenance and reliability remain unproven.
Verdict
Use with caution — the automation framework is well-structured and MIT licensed, but its low community adoption means you should carefully review its generated code and shell scripts before integrating it into sensitive workflows.
Claude Code-integrated React App Development Framework with 48 agents, Figma-to-React pipeline, and full product lifecycle support. Named after Marcus Aurelius.
Aurelius
A Claude Code-integrated multi-framework app development framework with TypeScript, Tailwind CSS, and automated design-to-code pipelines.
What This Framework Provides
- 48 Custom Agents -- Specialized AI agents for engineering, design, testing, marketing, operations, and more
- 17 Development Skills -- Automated workflows for Figma/Canva conversion, TDD, E2E testing, visual QA, state management, forms, auth, animation, SEO, and more
- 10-Phase Design-to-React Pipeline -- Convert Figma or Canva designs into fully working, tested React apps with a single command
- App-Type Awareness -- Tailored build and test strategies for web apps, Chrome extensions, and PWAs
- Testing Stack -- Vitest, React Testing Library, Playwright (cross-browser), Storybook, and pixel-diff visual QA
- Code Quality Scripts -- Linting, formatting, type checking, bundle analysis, accessibility scanning, and design token verification
Quick Start
# Clone the repository
git clone <repository-url>
cd aurelius
# Initialize a new project (Next.js or Vite)
./scripts/setup-project.sh my-app --vite # or --next
# Install dependencies
cd app && pnpm install
# Start development
pnpm dev
Build from Figma (Autonomous Pipeline)
/build-from-figma https://figma.com/file/abc123/My-Design
This runs a 10-phase autonomous pipeline:
[0] Token Sync → Drift check (conditional, if lockfile exists)
[1] Intake → Figma discovery + build-spec.json
[2] Token Lock → Design tokens lockfile + Tailwind config
[3] TDD (Gate) → Failing tests written first (mandatory)
[4] Build → React components that pass the tests
[5] Visual Diff → Pixel-level comparison loop (max 5 iterations, 2% threshold)
[6] E2E Tests → Playwright tests (app-type-aware)
[7] Cross-Browser→ Firefox/WebKit screenshots (non-blocking)
[8] Quality Gate → Coverage + TypeScript + build + tokens + Lighthouse + mutation score (opt-in)
[8.5] Responsive → Screenshots at 5 breakpoints (non-blocking)
[9] Report → Build report with diff images + component docs
Directory Structure
project-root/
├── app/ # Your application (generated by pipeline or setup script)
├── scripts/ # Automation scripts
│ ├── setup-project.sh # Initialize new project
│ ├── lint-and-format.sh # ESLint + Prettier
│ ├── run-tests.sh # Vitest with coverage
│ ├── check-types.sh # TypeScript type checking
│ ├── check-bundle-size.sh # Bundle size analysis
│ ├── check-accessibility.sh # a11y scanning
│ ├── verify-tokens.sh # Design token enforcement
│ ├── verify-test-coverage.sh # Component test verification
│ ├── visual-diff.js # Pixel-level screenshot comparison
│ ├── cross-browser-test.sh # Playwright multi-browser
│ ├── setup-playwright.sh # One-time browser setup
│ ├── check-dead-code.sh # Dead code detection (knip)
│ ├── check-security.sh # Dependency audit + anti-patterns
│ ├── generate-api-client.sh # OpenAPI → typed client
│ ├── check-responsive.sh # Responsive screenshots
│ ├── check-dark-mode.sh # Dark mode verification
│ ├── sync-tokens.sh # Token drift detection
│ ├── generate-stories.sh # Storybook story generation
│ └── generate-component-docs.sh # Component documentation
├── templates/ # Starter configs
│ ├── shared/ # ESLint, Prettier, Tailwind, TS, Vitest
│ ├── nextjs/ # Next.js config
│ ├── vite/ # Vite config
│ └── chrome-extension/ # Playwright E2E fixtures for extensions
├── docs/ # Documentation
│ ├── figma-to-react/ # Figma pipeline guide
│ ├── canva-to-react/ # Canva pipeline guide
│ └── react-development/ # Development standards
├── .claude/ # Claude Code configuration
│ ├── agents/ # 48 custom agents
│ ├── skills/ # 17 development skills
│ ├── commands/ # Slash commands (/build-from-figma, /lint, /test)
│ ├── pipeline.config.json # Pipeline thresholds and app-type definitions
│ ├── CUSTOM-AGENTS-GUIDE.md # Agent catalog
│ └── PLUGINS-REFERENCE.md # Plugin reference
├── CLAUDE.md # Claude Code project instructions
└── README.md # This file
Build from Canva (Autonomous Pipeline)
/build-from-canva https://www.canva.com/design/DAGxyz.../My-Design
Same 12-phase pipeline as Figma, with AI-powered token inference:
- Phase 1: Vision-based design discovery (screenshots + Claude analysis)
- Phase 2: AI token extraction with confidence scoring (requires user confirmation)
- Phases 3-9: Shared pipeline (TDD, build, visual diff, E2E, quality gate)
The Figma-to-React Pipeline
How It Works
The /build-from-figma command takes a Figma URL and autonomously builds a working React application through 10 phases. Key enforcement rules:
- TDD is mandatory -- Tests are written before components (Phase 3 gates Phase 4)
- Visual QA uses pixel diff --
pixelmatch-based comparison, not manual eyeballing - E2E tests are generated -- Tailored to app type (web app, Chrome extension, PWA)
- Design tokens are locked -- A lockfile prevents hardcoded values from entering components
Supported App Types
| App Type | Detection | E2E Strategy | Special Handling |
|---|---|---|---|
| Web App | Default | Page navigation, forms, responsive | Standard Playwright |
| Chrome Extension | manifest.json with manifest_version |
Extension load, popup, storage, content scripts | Persistent browser context with --load-extension |
| PWA | manifest.json with start_url |
Install prompt, offline fallback | Service worker and offline tests |
Pipeline Configuration
All thresholds and behavior are configurable in .claude/pipeline.config.json:
- Visual diff pass threshold (default: 2%)
- Max visual iterations (default: 5)
- TDD enforcement (default: on, non-negotiable)
- Coverage threshold (default: 80%)
- Lighthouse minimums (performance: 80, accessibility: 90)
- App-type-specific E2E strategies
48 Custom Agents
Agents are auto-selected by Claude Code based on your task:
| Category | Count | Key Agents |
|---|---|---|
| Engineering | 10 | frontend-developer, backend-architect, rapid-prototyper, test-writer-fixer, error-boundary-architect, migration-specialist, i18n-engineer |
| Design | 5 | ui-designer, ux-researcher, brand-guardian |
| Design-to-Code | 3 | figma-react-converter, canva-react-converter, asset-cataloger |
| Testing & QA | 7 | visual-qa-agent, accessibility-auditor, api-tester, performance-benchmarker |
| Product | 3 | sprint-prioritizer, feedback-synthesizer, trend-researcher |
| Marketing | 7 | content-creator, growth-hacker, app-store-optimizer |
| Project Mgmt | 3 | studio-producer, project-shipper, experiment-tracker |
| Operations | 5 | analytics-reporter, infrastructure-maintainer, legal-compliance-checker |
| Other | 5 | docusaurus-expert, agent-expert, command-expert, joker, studio-coach |
Full catalog: .claude/CUSTOM-AGENTS-GUIDE.md
17 Development Skills
Pipeline Skills (Phases 1-6)
| # | Skill | Purpose |
|---|---|---|
| 1 | figma-intake | Figma discovery + build-spec.json generation |
| 2 | design-token-lock | Extract and lock design tokens from Figma |
| 3 | tdd-from-figma | Write failing tests before components (app-type-aware) |
| 4 | figma-to-react-workflow | Generate components that pass the tests |
| 5 | visual-qa-verification | Pixel-diff comparison loop with region analysis |
| 6 | e2e-test-generator | Generate Playwright E2E tests (app-type-aware) |
Canva Pipeline Skills
| # | Skill | Purpose |
|---|---|---|
| 7 | canva-intake | Canva design discovery + build-spec.json generation |
| 8 | canva-token-inference | AI-powered token extraction from Canva screenshots |
React Development Skills
| # | Skill | Purpose |
|---|---|---|
| 9 | react-component-development | Component patterns, hooks, composition |
| 10 | react-testing-workflows | Vitest, RTL, Playwright, Storybook |
| 11 | react-performance-optimization | Profiling, bundle analysis, Web Vitals |
| 12 | react-accessibility | WCAG 2.1 AA patterns for React |
| 13 | state-management | Zustand, TanStack Query, URL state architecture |
| 14 | form-handling | React Hook Form + Zod: typed forms, wizards |
| 15 | auth-flows | Auth.js, Clerk, Supabase Auth, RBAC |
| 16 | animation-motion | Framer Motion, CSS transitions, reduced-motion a11y |
| 17 | seo-metadata | Next.js Metadata API, JSON-LD, OG images, sitemaps |
Full catalog: .claude/skills/README.md
Scripts
Code Quality
./scripts/lint-and-format.sh # ESLint + Prettier
./scripts/check-types.sh # TypeScript type checking
./scripts/check-bundle-size.sh # Bundle size analysis
./scripts/check-accessibility.sh # Automated a11y scanning
Testing
./scripts/run-tests.sh # Vitest unit/component tests
./scripts/cross-browser-test.sh # Playwright multi-browser screenshots
./scripts/setup-playwright.sh # One-time browser engine setup
Pipeline Verification
./scripts/verify-tokens.sh # Catch hardcoded design values
./scripts/verify-test-coverage.sh # Ensure every component has tests
node scripts/visual-diff.js --batch actual/ expected/ --json # Pixel diff
Full reference: scripts/README.md
Templates
Starter configuration files for new projects:
| Directory | Contents |
|---|---|
templates/shared/ |
ESLint, Prettier, Tailwind, TypeScript, Vitest configs |
templates/nextjs/ |
Next.js config |
templates/vite/ |
Vite config |
templates/chrome-extension/ |
Playwright E2E fixtures for Chrome extensions |
Full reference: templates/README.md
MCP Server Integration
The framework uses four MCP (Model Context Protocol) servers for Figma access, browser automation, and testing:
| Server | Purpose | Required For |
|---|---|---|
| Figma Desktop MCP | Read designs, extract tokens, capture screenshots from Figma | Phases 1-2, 5 |
| Figma Remote MCP | Fallback remote Figma access | Phases 1-2, 5 |
| Chrome DevTools MCP | Screenshots, Lighthouse audits, DOM inspection | Phases 5, 7-8 |
| Canva AI Connector | Search, export, interact with Canva designs | Phases 1-2 (Canva) |
| Playwright MCP | Cross-browser testing (Chromium, Firefox, WebKit) | Phases 6-7 |
MCP servers are configured in .claude/settings.json. Figma Desktop MCP requires the Figma desktop app running locally.
Claude Code Plugins
episodic-memory # Persistent memory across sessions
commit-commands # Git workflow automation (/commit, /commit-push-pr)
superpowers # Advanced development workflows (TDD, planning, debugging)
ai-taskmaster # Task management (local)
GitHub integration via gh CLI (not a plugin).
Details: .claude/PLUGINS-REFERENCE.md
Documentation Index
| Document | Location | Description |
|---|---|---|
| Developer onboarding | docs/onboarding/README.md |
Start here -- quickstart, architecture, configuration, troubleshooting |
| Quickstart guide | docs/onboarding/quickstart.md |
Clone to running project in 10 minutes |
| Architecture overview | docs/onboarding/architecture.md |
All 53 agents, 19 skills, 3 pipelines, and how they connect |
| Pipeline configuration | docs/onboarding/pipeline-configuration.md |
Every setting in pipeline.config.json explained |
| Troubleshooting FAQ | docs/onboarding/troubleshooting.md |
Common issues and solutions |
| Project instructions | CLAUDE.md |
Full project config for Claude Code |
| Figma pipeline guide | docs/figma-to-react/README.md |
Pipeline overview and troubleshooting |
| React standards | docs/react-development/README.md |
TypeScript, Tailwind, testing conventions |
| Canva pipeline guide | docs/canva-to-react/README.md |
Canva pipeline overview and troubleshooting |
| Agent catalog | .claude/CUSTOM-AGENTS-GUIDE.md |
All 53 agents with use cases |
| Skills catalog | .claude/skills/README.md |
All 19 skills with triggers |
| Plugin reference | .claude/PLUGINS-REFERENCE.md |
Plugin configuration and commands |
| Scripts reference | scripts/README.md |
All scripts with usage examples |
| Templates reference | templates/README.md |
Starter configs and how to use them |
| Pipeline config | .claude/pipeline.config.json |
Thresholds, app types, quality gates |
| Agent naming guide | .claude/AGENT-NAMING-GUIDE.md |
Conventions for creating new agents |
License
MIT
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi