Run any Skill in Manus with one click

Get Started

implement-phase

Stars0

Forks0

UpdatedMarch 5, 2026 at 17:30

Implement a numbered phase from docs/phases/phase-$ARGUMENTS.md step by step

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mkaraivanov

mkaraivanov/invoice-processor

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	implement-phase
description	Implement a numbered phase from docs/phases/phase-$ARGUMENTS.md step by step
disable-model-invocation	true
argument-hint	[phase-number]

Read @docs/phases/readme.md. You are about to implement Phase $ARGUMENTS.

Before you start

Locate the Phase $ARGUMENTS section. Read the ENTIRE phase — all subsections — before writing any code.
Scan the existing file tree with Glob to see what already exists. Do not recreate files; only fill in what is missing.
Install packages with npm install only (never yarn, pnpm, or bun).
If the phase involves Prisma schema changes, run the migration BEFORE touching source files.

Critical constraints — check on every file you write

Prisma

Import path: @/app/generated/prisma/client — NEVER @prisma/client
Enums (InvoiceStatus, etc.) also come from @/app/generated/prisma/client
Never instantiate PrismaClient outside src/lib/prisma.ts

Next.js 15

cookies() from next/headers is async — always await cookies()
Server Component params: const { id } = await params where params: Promise<{ id: string }>

Supabase SSR

Use @supabase/ssr only — never @supabase/auth-helpers-nextjs
Middleware setAll must set cookies on BOTH request AND response

Services and access control

Services import repositories, never prisma directly
Every data-access method must verify record.userId === requestingUserId before returning

File naming

Source files: kebab-case.ts / kebab-case.tsx
Components: PascalCase.tsx
Tests: *.spec.ts in tests/ (not co-located)

Implementation order

Follow the plan's numbered subsections in sequence — they are ordered by dependency.

After completing the phase

npx tsc --noEmit
npm run lint

Manual checklist:

All Prisma imports use @/app/generated/prisma/client
All cookies() calls are awaited
Every service method that accesses invoice data checks ownership
No .env or .env.local files were touched

Then invoke the code-review skill — a completed phase is a full feature boundary.

More from this repository

same repository

implement-test-phase

mkaraivanov/invoice-processor

Implement a numbered testing strategy phase from docs/testing_strategy_phases/phase_$ARGUMENTS_*.md step by step

2026-03-060

code-review

mkaraivanov/invoice-processor

Review changed code for correctness, security, and project conventions. Invoke this skill automatically whenever a complete unit of work is done — a full implementation phase, a complete feature (repository + service + route + component all connected), or just before creating a PR. Do NOT invoke after editing a single file or mid-way through a feature. If the user says "done", "finished", "phase complete", "ready to commit", or similar, trigger this review immediately.

2026-03-050

db-migrate

mkaraivanov/invoice-processor

Run prisma migrate dev, regenerate client to the correct output path, and verify import paths

2026-03-050

new-repository

mkaraivanov/invoice-processor

Scaffold a Prisma-backed repository for a given Prisma model

2026-03-050

new-service

mkaraivanov/invoice-processor

Scaffold a service class for a given domain following project conventions

2026-03-050

verify

mkaraivanov/invoice-processor

Final pre-commit check: run type-check (npx tsc --noEmit), lint (npm run lint), and tests (npm test)

2026-03-050

name	implement-phase
description	Implement a numbered phase from docs/phases/phase-$ARGUMENTS.md step by step
disable-model-invocation	true
argument-hint	[phase-number]

Read @docs/phases/readme.md. You are about to implement Phase $ARGUMENTS.

Before you start

Locate the Phase $ARGUMENTS section. Read the ENTIRE phase — all subsections — before writing any code.
Scan the existing file tree with Glob to see what already exists. Do not recreate files; only fill in what is missing.
Install packages with npm install only (never yarn, pnpm, or bun).
If the phase involves Prisma schema changes, run the migration BEFORE touching source files.

Critical constraints — check on every file you write

Prisma

Import path: @/app/generated/prisma/client — NEVER @prisma/client
Enums (InvoiceStatus, etc.) also come from @/app/generated/prisma/client
Never instantiate PrismaClient outside src/lib/prisma.ts

Next.js 15

cookies() from next/headers is async — always await cookies()
Server Component params: const { id } = await params where params: Promise<{ id: string }>

Supabase SSR

Use @supabase/ssr only — never @supabase/auth-helpers-nextjs
Middleware setAll must set cookies on BOTH request AND response

Services and access control

Services import repositories, never prisma directly
Every data-access method must verify record.userId === requestingUserId before returning

File naming

Source files: kebab-case.ts / kebab-case.tsx
Components: PascalCase.tsx
Tests: *.spec.ts in tests/ (not co-located)

Implementation order

Follow the plan's numbered subsections in sequence — they are ordered by dependency.

After completing the phase

npx tsc --noEmit
npm run lint

Manual checklist:

All Prisma imports use @/app/generated/prisma/client
All cookies() calls are awaited
Every service method that accesses invoice data checks ownership
No .env or .env.local files were touched

Then invoke the code-review skill — a completed phase is a full feature boundary.