web-architecture

What This Skill Does

The web-architecture skill provides a battle-tested framework for managing complex TypeScript, Next.js, and Convex projects through multi-agent orchestration. It is designed to prevent the 'partial code trap' where independent agents produce code that passes builds but fails functional requirements. The skill enforces a strict, phased development lifecycle that mandates a sequential bootstrapping phase to ensure schema integrity, type contracts, and shared initialization before allowing parallel feature development.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/michaelmonetized/web-architecture

Use Cases

• Complex Full-Stack Applications: Ideal for projects using Convex backend with Next.js frontends where strict schema adherence is required.
• Team Augmentation: Use this to orchestrate multiple agent workers on large refactors while ensuring the 'source of truth' for types remains consistent.
• Project Rescue: Apply this workflow to reorganize spaghetti codebases by forcing a Phase 0 bootstrap restart to clear integration errors.
• Scalable Feature Development: Use it to safely spawn sub-agents for UI component development once the data contracts are locked down.

Example Prompts

1. "Initialize a new project using the web-architecture bootstrap Phase 0. Ensure Convex is set up and generate the CONTRACTS.md file based on a user profile and order management schema."
2. "We have completed Phase 0. Please spawn three parallel agents to build the marketing dashboard, documentation pages, and static settings components as per the standards in STANDARDS.md."
3. "Review the current backend functions and identify if they conflict with our documented CONTRACTS.md. Update the agent workflow if we are drifting from the schema."

Tips & Limitations

• The Golden Rule: A single agent with full context will always outperform multiple agents with partial context. Use multi-agent delegation only for isolated, non-dependent tasks.
• No Timeouts: Ensure the execution environment does not kill sub-agents, as partial implementation is often worse than no implementation.
• Completion Check: Always verify functionality, not just successful builds. If the code compiles but the UI is a no-op, the phase is not complete.