ワンクリックでManusで任意のスキルを実行

fullstack-implementation

スター3

フォーク1

更新日2026年6月3日 05:24

Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

htooayelwinict

htooayelwinict/vibekit

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Fullstack Implementation

Use this skill when the task is to implement code, not just plan or advise.

Workflow

Identify the active plan from the user request, current context, or plan/*/plan.md; if several candidates exist, inspect their README.md or phase status before choosing.
Review the matching research/ notes and current phase file.
Follow existing repository patterns before introducing new structure.
If unfamiliar APIs, tricky behavior, or implementation trade-offs require external context and the user enabled a relevant MCP, load the matching mcp-* skill first. If crucial context is unavailable, state the assumption or ask a focused question.
Implement one phase or one tight slice at a time.
Run the narrowest relevant verification first, then broader checks. If verification fails, fix in-scope issues while the evidence points to the current change; record unrelated or environment-caused failures as blockers.
Update plan artifacts so another assistant can resume work later.

Required Plan-Aware Behavior

Treat plan/<topic>-<timestamp>/plan.md as the execution source of truth when a plan exists. If no plan exists and the task is small, proceed with local context; if the task is multi-step or risky, create or request planning artifacts first.
Update phase checklists or status markers when work completes.
Record blockers and deviations in the active phase file. Record long-term follow-up work in the active plan README.md or docs when it affects future work.
If implementation reveals missing context, add it to research/ instead of keeping it only in chat.

Relevant MCP Skills

mcp-context7 for official framework or library docs
mcp-github for PR, issue, workflow, or release context
mcp-figma for design-driven implementation details
mcp-playwright for browser verification and UI flows
mcp-sentry for production issue context tied to the change
mcp-open-bridge for implementation-option comparison, blocker analysis, and focused diff review

Output

Report with:

Active plan path
Phase completed or updated
Files changed
Verification run
Blockers or follow-ups

このリポジトリの他の Skills

同じリポジトリ

brainstorming

htooayelwinict/vibekit

Explore options, trade-offs, and decision paths without implementing code. Use when the user asks to brainstorm, compare approaches, choose architecture, or save a durable decision note.

2026-06-033

database-change-management

htooayelwinict/vibekit

Plan and implement safe schema, migration, relationship, index, query, and backfill changes with rollback awareness. Use when data shape or persistence contracts change.

2026-06-033

devops-infrastructure

htooayelwinict/vibekit

Manage deployment, Docker, CI/CD, environment, secrets, and infrastructure changes with rollback and verification. Use for operational config or release safety work.

2026-06-033

documentation-management

htooayelwinict/vibekit

Create, update, and audit durable project documentation. Use when code, setup, workflow, architecture, API behavior, or project structure must be reflected in docs.

2026-06-033

project-orchestration

htooayelwinict/vibekit

Coordinate multi-specialist work, handoffs, blockers, and durable progress artifacts. Use when tasks span roles, phases, or parallel workstreams.

2026-06-033

project-planning

htooayelwinict/vibekit

Create structured implementation plans with repository research, phased execution, risks, and verification. Use when work is unclear, risky, multi-file, or the user asks for a plan.

2026-06-033

Fullstack Implementation

Use this skill when the task is to implement code, not just plan or advise.

Workflow

Identify the active plan from the user request, current context, or plan/*/plan.md; if several candidates exist, inspect their README.md or phase status before choosing.

Review the matching research/ notes and current phase file.

Follow existing repository patterns before introducing new structure.

If unfamiliar APIs, tricky behavior, or implementation trade-offs require external context and the user enabled a relevant MCP, load the matching mcp-* skill first. If crucial context is unavailable, state the assumption or ask a focused question.

Implement one phase or one tight slice at a time.

Run the narrowest relevant verification first, then broader checks. If verification fails, fix in-scope issues while the evidence points to the current change; record unrelated or environment-caused failures as blockers.

Update plan artifacts so another assistant can resume work later.

Required Plan-Aware Behavior

Treat plan/<topic>-<timestamp>/plan.md as the execution source of truth when a plan exists. If no plan exists and the task is small, proceed with local context; if the task is multi-step or risky, create or request planning artifacts first.

Update phase checklists or status markers when work completes.

Record blockers and deviations in the active phase file. Record long-term follow-up work in the active plan README.md or docs when it affects future work.

If implementation reveals missing context, add it to research/ instead of keeping it only in chat.

Relevant MCP Skills

mcp-context7 for official framework or library docs

mcp-github for PR, issue, workflow, or release context

mcp-figma for design-driven implementation details

mcp-playwright for browser verification and UI flows

mcp-sentry for production issue context tied to the change

mcp-open-bridge for implementation-option comparison, blocker analysis, and focused diff review

Output

Report with:

Active plan path

Phase completed or updated

Files changed

Verification run

Blockers or follow-ups

name	fullstack-implementation
description	Implement planned product or code changes phase by phase using repo patterns and verification. Use when the user asks to build, modify, or finish implementation work.