alain.bagmi/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9c1bf0a285
skills/amplify-workflow/references/backend.md

2.2 KiB
Raw Blame History

Backend Phase Instructions

Create or modify Amplify Gen 2 backend resources.

Prerequisites Confirmed

Prerequisites (Node.js, npm, AWS credentials) were already validated by the orchestrator workflow. Do not re-validate.

Critical Constraints

  • Do NOT create frontend scaffolding or templates during this phase. Do not run create-next-app, create-react-app, create-vite, npm create, or any frontend project generators. This phase is strictly for Amplify backend resources (the amplify/ directory). If a frontend project already exists, leave it untouched. If no frontend project exists and the user only asked for backend work, do NOT create one.

  • Before creating any files, ensure .gitignore exists in the project root and includes: node_modules/, .env*, amplify_outputs.json, .amplify/, dist/, build/. Create or update it if these entries are missing.

Retrieve and Follow the SOP

Do NOT write any code until you have retrieved and read the SOP.

Use the SOP retrieval tool to get "amplify-backend-implementation" and follow it completely.

If SOP retrieval fails (empty result, error, or timeout), STOP and inform the user: "I couldn't retrieve the backend implementation guide. Please verify that the aws-mcp server is active and try again." Do NOT attempt to write backend code from general knowledge.

SOP Overrides

  • Skip the SOP's Step 1 ("Verify Dependencies") -- prerequisites were already validated by the orchestrator.
  • Skip the SOP's Step 12 ("Determine Next SOP Requirements") -- phase sequencing is controlled by the orchestrator workflow, not the SOP.

Follow all other SOP steps (2 through 11) completely. Do not improvise or skip them.

Error Handling

  1. If you encounter an error, fix the immediate issue
  2. Return to the SOP and continue from where you left off
  3. Do NOT abandon the SOP or start improvising
  4. If you lose track, retrieve the SOP again, identify your last completed step, and continue

Phase Complete

After the SOP is fully executed, summarize what was created (which resources, files, configurations).

This phase is now complete. Do not read other reference files or proceed to the next phase — return control to the orchestrator workflow (SKILL.md).