Package Exports

ridulian-lib
ridulian-lib/bin/install.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ridulian-lib) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Ridulian Lib

Claude Code skills for orchestrated agent teams. One command installs a CEO, a CTO with six tech specialists (Python, Full Stack, Frontend, Backend, Mobile, DevOps), and a CMO with a design lead and five marketing/design specialists (Brand, UX, UI, Copy, Motion) — all into your global ~/.claude/skills/.

Install

npx -y ridulian-lib

That's it. Run it once on any machine with Node ≥18 and Claude Code installed; every skill becomes invokable as /ceo, /cto, /tech-python, /cmo, etc.

Flags

Flag	What it does
`--list`	Show every skill in the package without installing
`--dry-run`	Show what would be installed (or overwritten)
`--bundle <name>`	Install one web-app bundle only (e.g. `--bundle marketingskills`)
`--general-only`	Install only the role skills in `general_purpose/` (skip web-app bundles)
`--force`	Overwrite existing skills without prompt

npx -y ridulian-lib --bundle marketingskills
npx -y ridulian-lib --general-only --force
npx -y ridulian-lib --list

What you get

General-purpose orchestration chain

Skill	Role
`ceo`	Entry point for any feature in any repo. Asks clarifying questions + auto-discovers the repo's stack/conventions, then dispatches the CTO and/or CMO arm and the reviewer.
`cto`	Decomposes the CEO brief into a dependency-ordered tech task list and dispatches each task to the right tech specialist.
`tech-python`	Django, FastAPI, Flask, scripts, data tools, ML utilities.
`tech-fullstack`	Next.js / Remix / SvelteKit, tRPC + React, Prisma + Express.
`tech-frontend`	Pure UI: React/Vue/Svelte/Solid, CSS/Tailwind, accessibility.
`tech-backend`	Non-Python backend: Node, Go, Rust, Ruby, Java/Kotlin.
`tech-mobile`	iOS Swift/SwiftUI, Android Kotlin/Compose, React Native, Flutter.
`tech-devops`	CI/CD, Docker, K8s, Terraform, observability.
`cmo`	Decomposes the CEO brief into marketing/design sub-tasks. Dispatches single-discipline copy/brand/motion specialists directly; delegates multi-discipline design briefs to `design-lead`.
`design-lead`	Sub-orchestrator under CMO. Decomposes complex design briefs spanning brand + UX + UI + motion and dispatches each piece to the right design specialist.
`design-brand`	Brand identity, logos, visual systems, color palettes, typography pairs, brand guidelines.
`design-ux`	User research, flows, information architecture, wireframes, journey maps, usability.
`design-ui`	High-fidelity visual design, design systems, components, design tokens, mockups, dark mode.
`design-copy`	Copywriting, tone of voice, marketing content, microcopy, UI strings, naming.
`design-motion`	Motion design, animation, video, micro-interactions, transitions, Lottie.

Project-specific bundles

Bundle	Skills
`marketingskills`	41 vendored marketing/CRO/SEO/copy/RevOps specialists. Source: github.com/coreyhaines31/marketingskills (MIT, © 2025 Corey Haines).
`understand-anything`	9 vendored codebase-analysis agents (architecture-analyzer, project-scanner, knowledge-graph-guide, etc.). Source: github.com/Lum1104/Understand-Anything (MIT, © 2026 Yuxiang Lin).

Vendored bundles + licenses

This package vendors two external skill collections so they ship via the same npx install. Both are MIT-licensed; LICENSE files are preserved alongside their skills:

marketingskills at web_app_prompts/marketingskills/ — copyright © 2025 Corey Haines. Source: https://github.com/coreyhaines31/marketingskills
understand-anything at web_app_prompts/understand-anything/ — copyright © 2026 Yuxiang Lin. Source: https://github.com/Lum1104/Understand-Anything

The Ridulian-Lib skills-catalog (loaded automatically by /ceo) tells orchestrators when to prefer a vendored external skill over a Ridulian native specialist.

How the orchestration chain works

The chain is two layers — a product layer (CEO) and execution arms (CTO for engineering, CMO for marketing/design). Each handoff happens in isolated subagent context (no prior conversation leakage). The CEO spawns whichever arms the brief requires; for tech-only or design-only briefs, only one arm runs. The orchestrator the user invokes is always CEO (or a project-specific PM where one exists).

user → /ceo
         │
         ├─ Phase 1: Q&A + repo recon → confirmed brief
         │
         └─ Phase 2: spawn /cto and/or /cmo (isolated subagents)
                    │
                    ├─ /cto  ──► decomposes tech tasks
                    │             T1 → tech-python
                    │             T2 → tech-frontend
                    │             T3 → tech-devops  ...
                    │             each specialist runs isolated, returns: files-changed, verify, integration-notes
                    │
                    └─ /cmo  ──► decomposes marketing/design tasks
                                  M1 → design-copy           (single-discipline, dispatched direct)
                                  M2 → design-lead           (multi-discipline)
                                          ├─ D1 → design-brand
                                          ├─ D2 → design-ux
                                          ├─ D3 → design-ui
                                          └─ D4 → design-motion
                                  M3 → design-brand          (single-discipline, dispatched direct)
                                  each specialist runs isolated, returns: files-changed, verify, integration-notes
                    │
              ← rolls up to CEO
              CEO spawns reviewer → opens PR → returns URL to user

Each agent has a strict input/output contract so the next link in the chain gets exactly what it needs and nothing else.

Worktree convention

Orchestrators create git worktrees inside the repo at worktrees/{branch} (gitignored via .git/info/exclude) instead of polluting the parent directory with ../feature-x siblings. The .handoffs/ folder inside each worktree carries briefs/specs/task-lists between agents and is also excluded from commits.

Adding your own skills

Drop a .md file with YAML frontmatter into general_purpose/ (cross-project) or web_app_prompts/<your-app>/ (project-scoped):

---
name: my-skill
description: One-line trigger description Claude uses to decide when to invoke this skill.
---

You are a {role}. ...

Run npx ridulian-lib --force (or just node bin/install.js --force if you've cloned). Your new skill is now globally available.

The installer parses the YAML name: field and writes ~/.claude/skills/<name>/SKILL.md.

Local development

git clone https://github.com/Angroys/Ridulian-Lib.git
cd Ridulian-Lib
node bin/install.js --dry-run   # preview
node bin/install.js --force      # actually install

License

MIT.