meta-skills/full-stack-builder/SKILL.md
Build complete full-stack applications end-to-end using orchestrated skills
npx skillsauth add abcnuts/manus-skills full-stack-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Meta-Skill that orchestrates multiple skills to build complete full-stack applications from concept to deployment.
This meta-skill chains together 7+ individual skills to create a complete application workflow. It handles everything from requirements gathering to deployment, using the skill registry and composer to intelligently orchestrate the process.
python3 /tmp/manus-skills-v2/meta-skills/full-stack-builder/scripts/build_app.py "SaaS app with auth and payments"
from lib.skill_registry import SkillRegistry
from lib.skill_composer import SkillComposer
registry = SkillRegistry()
composer = SkillComposer(registry)
# Define workflow
workflow_skills = [
"brainstorming",
"database-schema-generator",
"api-endpoint-builder",
"user-authentication-system",
"testing-framework",
"deployment-automation"
]
# Compose and execute
workflow = composer.compose_workflow(workflow_skills)
results = composer.execute_workflow(workflow, {"description": "My SaaS App"})
Total: 30-35 hours per application
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code