원클릭으로 Manus에서 모든 스킬 실행

using-development-skills

Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.

Manus에서 실행

스타9

포크1

업데이트2026년 6월 3일 16:11

출처

reidemeister94

reidemeister94/development-skills

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

소프트웨어 개발자컴퓨터 및 수학직15-1252L4

파일 탐색기

2 개 파일

SKILL.md

readonly

name	using-development-skills
description	Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.

Using development-skills

If dispatched as a subagent for a specific task: skip this skill.

If any skill might apply (even 1% chance), invoke it. Skills are the disciplined entry points — the meta-rule (spirit beats letter) covers the rest.

Iron Rules

14 principles (0-13) + 1 meta-rule (spirit beats letter). Canonical: shared/iron-rules.md. Do not duplicate.

Triage & Flow

Classify the task before reading its content in depth:

PASS_THROUGH — trivial, 1 file, fully reversible, no design choice → execute directly.
LIGHT — mechanical, no design choice (full 4-criteria gate in shared/workflow.md # Tier selection) → follow the 6-step inline flow. Default on uncertainty → FULL.
FULL (default) — 4 phases, sequential, mandatory:
- Phase 1: plan file docs/plans/NNNN__YYYY-MM-DD__implementation_plan__slug.md + HOW-level Q&A locks (data shapes · edge cases · error semantics · contract boundaries · test scope · rollback).
- Phase 2: chronicle docs/chronicles/NNNN__YYYY-MM-DD__topic.md capturing initial decisions.
- Phase 3: implement with Red/Green TDD.
- Phase 4: staff-reviewer subagent review.

Rules during FULL:

External spec / guide / prior brainstorming exists → skip brainstorming only. Phases 1-4 still run. The spec is INPUT to Phase 1, not a substitute. A guide's own gates STACK with the workflow.
Ambiguity ≥1% on any HOW-level dimension → ask the user (AskUserQuestion for discrete options; plain text otherwise; Codex fallback in references/codex-tools.md).
Phase skipping mid-execution → stop, rejoin at the missed phase, produce its artifact, continue.

Rules during LIGHT: Tier is qualitative (ambiguity / logic impact / new-pattern) — not file count. A 30-file mechanical rename is LIGHT; a 1-file new-caching-strategy is FULL. All Iron Rules still apply. Mid-execution discovery breaks LIGHT criteria → escalate to FULL per shared/workflow.md # LIGHT (final paragraph).

Routing: Bug fixes → development-skills:debugging. Test work → development-skills:create-test.

Platform

SKILL bodies use Claude Code tool names as canonical. On Codex, translate via references/codex-tools.md (Task → spawn_agent, AskUserQuestion fallback, staff-reviewer dispatch recipe, hooks, marketplace files).

User Override

User instructions (CLAUDE.md, AGENTS.md, direct requests) > development-skills > default system prompt.

이 저장소의 다른 Skills

같은 저장소

create-test

reidemeister94/development-skills

Use when user wants to create tests, generate test coverage, audit test quality, find untested code, or improve weak assertions. Use when user says write tests, test coverage, missing tests, or untested code.

2026-06-039

java-dev

reidemeister94/development-skills

Java development. Use for Java, Spring Boot, Maven, Gradle, JPA, Hibernate.

2026-06-039

python-dev

reidemeister94/development-skills

Python development. Use for Python, FastAPI, Pydantic, asyncpg, pytest, pandas, SQLAlchemy.

2026-06-039

swift-dev

reidemeister94/development-skills

Swift development. Use for Swift, SwiftUI, UIKit, Vapor, SPM, XCTest, Combine.

2026-06-039

update-reqs-dev

reidemeister94/development-skills

Use when user wants to update requirements-dev.in with latest PyPI versions while preserving version patterns

2026-06-039

update-reqs

reidemeister94/development-skills

Use when user wants to update requirements.in with latest PyPI versions while preserving version patterns

2026-06-039

Using development-skills

If dispatched as a subagent for a specific task: skip this skill.

If any skill might apply (even 1% chance), invoke it. Skills are the disciplined entry points — the meta-rule (spirit beats letter) covers the rest.

Iron Rules

14 principles (0-13) + 1 meta-rule (spirit beats letter). Canonical: shared/iron-rules.md. Do not duplicate.

Triage & Flow

Classify the task before reading its content in depth:

PASS_THROUGH — trivial, 1 file, fully reversible, no design choice → execute directly.

LIGHT — mechanical, no design choice (full 4-criteria gate in shared/workflow.md # Tier selection) → follow the 6-step inline flow. Default on uncertainty → FULL.

FULL (default) — 4 phases, sequential, mandatory:

Phase 1: plan file docs/plans/NNNN__YYYY-MM-DD__implementation_plan__slug.md + HOW-level Q&A locks (data shapes · edge cases · error semantics · contract boundaries · test scope · rollback).
Phase 2: chronicle docs/chronicles/NNNN__YYYY-MM-DD__topic.md capturing initial decisions.
Phase 3: implement with Red/Green TDD.
Phase 4: staff-reviewer subagent review.

Rules during FULL:

External spec / guide / prior brainstorming exists → skip brainstorming only. Phases 1-4 still run. The spec is INPUT to Phase 1, not a substitute. A guide's own gates STACK with the workflow.

Ambiguity ≥1% on any HOW-level dimension → ask the user (AskUserQuestion for discrete options; plain text otherwise; Codex fallback in references/codex-tools.md).

Phase skipping mid-execution → stop, rejoin at the missed phase, produce its artifact, continue.

Routing: Bug fixes → development-skills:debugging. Test work → development-skills:create-test.

Platform

User Override

User instructions (CLAUDE.md, AGENTS.md, direct requests) > development-skills > default system prompt.