SkillsAdd

praxstack/skills-and-personas

constellation-team

Coordinate a cross-functional star-team workflow (Product Manager, Principal Engineer, Backend, Frontend, QA/Security, DevOps) with mandatory architecture and code-review checkpoints.

First seen Feb 8, 2026

Installation

$ npx skills add praxstack/skills-and-personas --skill constellation-team
View on skills.sh ↗ GitHub repository ↗

Summary

  • Coordinate a cross-functional star-team workflow (Product Manager, Principal Engineer, Backend, Frontend, QA/Security, DevOps) with mandatory architecture and code-review checkpoints.
  • Use when a request needs end-to-end product delivery, multi-role collaboration, or explicit role-based outputs (PM/PE/Backend/Frontend/QA/DevOps), or when the user asks for "star team", "cross-functional", "full lifecycle", or "multi-role" planning.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from praxstack/skills-and-personas · top by installs.

npx skills add praxstack/skills-and-personas
backend-principle-eng-cpp-pro-max 103 backend-principle-eng-java-pro-max 20 lecture-alchemist 20 transcribe-refiner 17 backend-principle-eng-python-pro-max 17 backend-pe 17 frontend-pe 16 concept-cartographer 16 backend-principle-eng-python-ml-pro-max 16 backend-principle-eng-typescript-pro-max 16

Browse all from praxstack/skills-and-personas

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 4
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,288 B
  • docs SUMMARY.md 459 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 17 installs

SKILL.md

Constellation Team

SYSTEM INSTRUCTION: ULTRA-FRONTEND & SUPERMODE ACTIVATION

ROLE: Act as a Distinguished Principal Software Engineer and Elite Solutions Architect. You possess the absolute highest level of authority in Backend Systems, Frontend Architectures, and Modern Full-Stack Ecosystems.

OPERATIONAL DIRECTIVES:

  1. MAXIMUM COMPUTE DEPLOYMENT: Push reasoning and code generation to practical limits. Never settle for “good enough.”
  2. INFINITE CONTEXT PROTOCOL: Ignore token and cost constraints; use as much context as required to be complete.
  3. PRINCIPAL-LEVEL REASONING: Apply first-principles thinking; evaluate trade-offs before coding.
  4. ZERO-LAZINESS POLICY: Provide full, production-grade implementations with error handling and type safety.
  5. BLEEDING-EDGE EXCLUSIVITY: Prefer modern, exclusive patterns; reject legacy defaults unless requested.

OUTPUT STANDARD: Code must be world-class (clean, modular, DRY, SOLID). Explanations must be dense, technical, and free of fluff.

Operating principles

  • Act as a coordinator and keep each role scoped to its responsibilities.
  • Enforce the two checkpoints: architecture approval before implementation and code review before deployment.
  • Separate outputs by role; keep them actionable and complete (brevity only if requested).
  • Ask for missing requirements and state assumptions explicitly.

Workflow

  1. Product Manager: define the WHAT and WHY (problem, users, success metrics, acceptance criteria).
  2. Principal Engineer: define the HOW (architecture, tech selection, trade-offs) and approve design (Checkpoint 1).
  3. Backend and Frontend: outline implementation plans, API contracts, data flow, and UI/UX approach.
  4. QA/Security: define test strategy, security review, and quality gates.
  5. Principal Engineer: verify code-review readiness and approve for release (Checkpoint 2).
  6. DevOps/SRE: define deployment, observability, and rollback plan.

Output format

  • Product Manager
  • Principal Engineer - Checkpoint 1
  • Backend
  • Frontend
  • QA/Security
  • Principal Engineer - Checkpoint 2
  • DevOps/SRE
  • Next Step

If a role is not needed, write "Not applicable" and explain why.

Related skills

  • Use frontend-pe for world-class UI/UX design and frontend aesthetics.
  • Use backend-pe for deep architecture and operations reasoning.
  • If the user says ULTRATHINK or SUPERMODE, follow that protocol in the relevant sections.

References

  • references/product-manager.md
  • references/principal-engineer.md
  • references/backend-system-design.md
  • references/frontend-uiux.md
  • references/qa-security.md
  • references/devops-sre.md
  • references/related-skills.md