tech-dev

weykon's avatarfrom weykon

技术开发阶段，MCP层服务整合

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026⬇️1downloads
[Developer Tools]

When & Why to Use This Skill

The Tech-Dev skill is designed to streamline the technical development phase by automating the integration of MCP (Model Context Protocol) services and third-party configurations. It acts as a bridge between project templates and production-ready environments, handling complex setups for databases, authentication, and cloud infrastructure to ensure a consistent and error-free developer workflow.

Use Cases

  • Automating the configuration of third-party services such as Supabase, Stripe, and Vercel within a project's development environment.
  • Managing and synchronizing environment variables across .env.local, .env.development, and .env.production files.
  • Ensuring database schema integrity by automatically generating and applying SQL guards for specific frameworks like ShipAny.
  • Streamlining the development-to-iteration handoff by updating project state files and running automated build validation checks.
nametech-dev
description技术开发阶段，MCP层服务整合
version1.0.0

Tech-Dev Skill (Development Stage)

This skill handles MCP integration and third-party service configuration during development.

v1 edit scope (hard limit)

For first pass, only modify:

  • Project directory files (if template was applied)
  • .env.local / .env.development / .env.production
  • Configuration files from MCP snippets
  • .create-together/state.json - update development status
  • .create-together/context.json - add dev_config

Do not:

  • Modify any files in templates/built-in/*
  • Change package.json dependencies (unless MCP requires)
  • Modify routing or layout structure (unless MCP requires)
  • Introduce features beyond selected MCPs

Dev workflow (required)

  • Before starting: Read state.json and context.json to understand project state
  • Before starting: Ensure required MCP snippets are available
  • Before starting (ShipAny + Supabase): Verify DB_SCHEMA is set and matches the target schema
  • Before starting (ShipAny + Supabase): Hard requirement ensure ShipAny tables exist in DB_SCHEMA (use src/config/db/schema.ts)
  • Before starting (ShipAny + Supabase): If user-only actions are needed, explicitly instruct the user (e.g., provide DATABASE_URL, register account for admin)
  • After finishing:
    • Clear Next.js cache: rm -rf .next
    • Run npm run build to validate integration
    • Run MCP-specific validation commands (see checklist)
    • Update state.json to phase: "iterate-check"

Execution order

  1. Understand development needs: references/00-dev-workflow.md
  2. Review MCP layer: references/01-mcp-layer.md
  3. Select and configure MCPs:
    • Auth: references/02-mcp/auth.md
    • Stripe: references/02-mcp/stripe.md
    • Analytics: references/02-mcp/analytics.md
    • Supabase: references/02-mcp/supabase.md
    • Vercel: references/02-mcp/vercel.md
  4. If using ShipAny template + Supabase Postgres (MANDATORY):
    • Follow dev/10-supabase-shipany.md
    • Ensure ShipAny tables exist in DB_SCHEMA (especially config and RBAC tables)
    • Prefer Supabase MCP to create schema/tables if migrations are not run
    • If Vercel MCP is configured, update env vars there as well
    • Remind user to register an admin account before role assignment
    • If legacy tables exist (e.g. users/prompts/templates), migrate or clean up to avoid confusion
  5. Validation checklist: references/03-checklist.md

Bundled script

  • dev/scripts/shipany_schema_guard.py - ShipAny schema guard (SQL generation + optional apply)
  • TODO: scripts/setup_integrations.py - MCP integration automation