Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

architect-builder-method

Étoiles0

Forks0

Mis à jour20 mai 2026 à 11:12

Use when building software with AI by separating Architect (planning) from Builder (implementation), with files as source of truth instead of chat history.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

jpoindexter

jpoindexter/theft-kit

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	architect-builder-method
description	Use when building software with AI by separating Architect (planning) from Builder (implementation), with files as source of truth instead of chat history.

Architect Builder Method

Use this skill when the user is shipping software through AI tools and wants less "vibe coding" and more predictable delivery.

Core model

Architect layer: reasoning/planning model produces structure, requirements, and handoff.
Builder layer: coding agent executes against that handoff.
Source of truth: project files/folders, not chat scrollback.

Workflow

Clarify business outcome and target user workflow.
Convert raw idea into builder-ready artifacts.
Hand builder a scoped sprint packet.
Build, verify, record decisions, and repeat.

Non-negotiables

Do not let builder infer missing business rules silently.
Define what "done" means before implementation starts.
Keep durable decisions in files, not memory or chat.

Output contract

Produce:

A concise objective
Explicit constraints
Acceptance criteria
A builder handoff prompt

Plus depuis ce dépôt

même dépôt

managing-context-window

jpoindexter/theft-kit

Use when a conversation is getting long, drifting, juggling multiple tasks, re-pasting the same files, or showing stale/confused context — and at the start of any new task. Triggers: long thread, context bloat, topic switch, repeated file uploads, 'why is it forgetting', degraded answers, finished one task and starting another.

2026-06-010

first-principles-deconstructor

jpoindexter/theft-kit

Use when a user wants to deconstruct a complex problem, business challenge, product decision, strategy question, career crossroads, or stuck situation by stripping assumptions, identifying first principles, rebuilding options from foundational truths, and choosing one high-leverage action.

2026-05-210

access-control-audit

jpoindexter/theft-kit

Audit role-based access control and permission drift across product surfaces.

2026-05-200

add-package-feature

jpoindexter/theft-kit

Add a new feature to an existing @fabrk/* package following monorepo conventions

2026-05-200

adr-index

jpoindexter/theft-kit

Build or rebuild the ADR index and dependency graph in AgentDB

2026-05-200

agentdb-query

jpoindexter/theft-kit

Query AgentDB with semantic routing, hierarchical recall, causal graphs, and context synthesis

2026-05-200

name	architect-builder-method
description	Use when building software with AI by separating Architect (planning) from Builder (implementation), with files as source of truth instead of chat history.

Architect Builder Method

Use this skill when the user is shipping software through AI tools and wants less "vibe coding" and more predictable delivery.

Core model

Architect layer: reasoning/planning model produces structure, requirements, and handoff.
Builder layer: coding agent executes against that handoff.
Source of truth: project files/folders, not chat scrollback.

Workflow

Clarify business outcome and target user workflow.
Convert raw idea into builder-ready artifacts.
Hand builder a scoped sprint packet.
Build, verify, record decisions, and repeat.

Non-negotiables

Do not let builder infer missing business rules silently.
Define what "done" means before implementation starts.
Keep durable decisions in files, not memory or chat.

Output contract

Produce:

A concise objective
Explicit constraints
Acceptance criteria
A builder handoff prompt