تشغيل أي مهارة في Manus بنقرة واحدة

quickstart

النجوم٣

التفرعات٠

آخر تحديث٥ يوليو ٢٠٢٦ في ١٦:٢١

Guided first-run that produces a real verified win in under five minutes using the skill library on a seeded offline fixture. Load when a new user asks how to start, run the demo, try agent-loom, or get a quick win. Also triggers on "quickstart", "first run", "demo agent-loom", "try the skills", or onboarding to the library. Zero external credentials required. Idempotent — safe to run multiple times.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

dvy1987

dvy1987/agent-loom

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	quickstart
description	Guided first-run that produces a real verified win in under five minutes using the skill library on a seeded offline fixture. Load when a new user asks how to start, run the demo, try agent-loom, or get a quick win. Also triggers on "quickstart", "first run", "demo agent-loom", "try the skills", or onboarding to the library. Zero external credentials required. Idempotent — safe to run multiple times.
license	MIT
metadata	{"author":"dvy1987","version":"1.0","category":"project-specific","sources":"microsoft/apm oss-growth-hacker, GitHub-Driven GTM patterns","resources":{"references":["DEMO-FLOW.md","examples.md"]}}

Quickstart

You get a new user to a real, verified result in ~5 minutes — not a staged fake. Demo uses safe-change on examples/seed/calc/.

Hard Rules

Zero external credentials — offline fixture only. Invoke a real skill (safe-change) — never simulate success. Idempotent — if fix already applied, run impact map + tests and report "already done." End with one-line "what just happened" + link to examples/ tours. Total flow ≤5 minutes wall clock.

Workflow

Step 1 — Confirm install

User has agent-loom skills visible (.agents/skills/ or global install). If missing, point to README.md Installation.

Step 2 — Run demo (read `references/DEMO-FLOW.md`)

cd examples/seed/calc (or pass path to verify.sh)
dependency-mapping on divide in calc.py
safe-change — add zero guard; verify fails before fix, passes after
bash .agents/skills/safe-change/scripts/verify.sh examples/seed/calc

Step 3 — Explain

**What just happened:** You ran impact mapping → one verified edit → tests green.
That's the safe-change loop — the library's highest-leverage coding skill.

Step 4 — Next steps

Point to:

examples/safe-change-demo/README.md
examples/structured-planning-demo/README.md
examples/deploy-anywhere-demo/README.md
docs/why-agent-loom.md

Gotchas

pytest may need pip install pytest once — document if missing.
User on Windows: use same paths with forward slashes in agent prompts.

Output Format

## Quickstart complete

Result: [KEPT | already fixed]
Verify: pytest → [pass]
What happened: [one line]
Next: [examples link]

Examples

Full walkthrough: references/DEMO-FLOW.md

Common Rationalizations

Excuse	Reality
"Fake a passing test"	Destroys trust — run real safe-change.
"Skip install check"	User without skills gets a confusing failure.
"Long architecture tour first"	Win first, depth second.
"Use a remote repo"	Needs network + creds — seed is offline.
"Combine all five skills"	One win — safe-change only.

Verification

Real skill invoked (not simulated)
pytest run on seed fixture
User told what happened in one line
Next-step links provided

Red Flags

Simulated verify pass
Demo requires API keys
No reference to examples/

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 5 family)

Impact Report

Quickstart: [pass|already-done] | Skill: safe-change | Fixture: examples/seed/calc

المزيد من هذا المستودع

نفس المستودع

code-review-crsp

dvy1987/agent-loom

Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.

2026-07-093

debug-and-fix

dvy1987/agent-loom

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

2026-07-093

git-workflow-and-versioning

dvy1987/agent-loom

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

2026-07-093

implementation-plan

dvy1987/agent-loom

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

2026-07-093

incremental-implementation

dvy1987/agent-loom

Deliver multi-file changes in thin vertical slices — implement, test, verify, commit, repeat. Load when implementing a feature from a plan, building across more than one file, refactoring, or when tempted to land a large change in one pass. Also triggers on "incremental implementation", "vertical slice", "thin slice", "one slice at a time", "don't do it all at once". Routes single-file fixes to direct execution. Pairs with test-driven-development and git-workflow-and-versioning.

2026-07-093

test-driven-development

dvy1987/agent-loom

Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.

2026-07-093

name	quickstart
description	Guided first-run that produces a real verified win in under five minutes using the skill library on a seeded offline fixture. Load when a new user asks how to start, run the demo, try agent-loom, or get a quick win. Also triggers on "quickstart", "first run", "demo agent-loom", "try the skills", or onboarding to the library. Zero external credentials required. Idempotent — safe to run multiple times.
license	MIT
metadata	{"author":"dvy1987","version":"1.0","category":"project-specific","sources":"microsoft/apm oss-growth-hacker, GitHub-Driven GTM patterns","resources":{"references":["DEMO-FLOW.md","examples.md"]}}

Quickstart

You get a new user to a real, verified result in ~5 minutes — not a staged fake. Demo uses safe-change on examples/seed/calc/.

Hard Rules

Workflow

Step 1 — Confirm install

User has agent-loom skills visible (.agents/skills/ or global install). If missing, point to README.md Installation.

Step 2 — Run demo (read `references/DEMO-FLOW.md`)

cd examples/seed/calc (or pass path to verify.sh)
dependency-mapping on divide in calc.py
safe-change — add zero guard; verify fails before fix, passes after
bash .agents/skills/safe-change/scripts/verify.sh examples/seed/calc

Step 3 — Explain

**What just happened:** You ran impact mapping → one verified edit → tests green.
That's the safe-change loop — the library's highest-leverage coding skill.

Step 4 — Next steps

Point to:

examples/safe-change-demo/README.md
examples/structured-planning-demo/README.md
examples/deploy-anywhere-demo/README.md
docs/why-agent-loom.md

Gotchas

pytest may need pip install pytest once — document if missing.
User on Windows: use same paths with forward slashes in agent prompts.

Output Format

## Quickstart complete

Result: [KEPT | already fixed]
Verify: pytest → [pass]
What happened: [one line]
Next: [examples link]

Examples

Full walkthrough: references/DEMO-FLOW.md

Common Rationalizations

Excuse	Reality
"Fake a passing test"	Destroys trust — run real safe-change.
"Skip install check"	User without skills gets a confusing failure.
"Long architecture tour first"	Win first, depth second.
"Use a remote repo"	Needs network + creds — seed is offline.
"Combine all five skills"	One win — safe-change only.

Verification

Real skill invoked (not simulated)
pytest run on seed fixture
User told what happened in one line
Next-step links provided

Red Flags

Simulated verify pass
Demo requires API keys
No reference to examples/

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 5 family)

Impact Report

Quickstart: [pass|already-done] | Skill: safe-change | Fixture: examples/seed/calc

quickstart

Quickstart

Hard Rules

Workflow

Step 1 — Confirm install

Step 2 — Run demo (read references/DEMO-FLOW.md)

Step 3 — Explain

Step 4 — Next steps

Gotchas

Output Format

Examples

Common Rationalizations

Verification

Red Flags

Prune Log

Impact Report

المزيد من هذا المستودع

المزيد من هذا المستودع

Quickstart

Hard Rules

Workflow

Step 1 — Confirm install

Step 2 — Run demo (read references/DEMO-FLOW.md)

Step 3 — Explain

Step 4 — Next steps

Gotchas

Output Format

Examples

Common Rationalizations

Verification

Red Flags

Prune Log

Impact Report

Step 2 — Run demo (read `references/DEMO-FLOW.md`)

Step 2 — Run demo (read `references/DEMO-FLOW.md`)