AGENT SKILL

greenfield-product

Greenfield product intake when user wants to build a new app (notes, todo, SaaS, API). Recommend stack, gather requirements, scaffold, then small-task orchestra loops until production. Use for "build a note app", "new project", "from scratch", "let's build".

License 许可
MIT
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
greenfield-product
description
Greenfield product intake when user wants to build a new app (notes, todo, SaaS, API). Recommend stack, gather requirements, scaffold, then small-task orchestra loops until production. Use for "build a note app", "new project", "from scratch", "let's build".

03 SKILL.md 正文

Greenfield product → production loop

Triggered when orchestra classifies greenfield (build a … app, new project, from scratch).

Flow

User idea
  → Present recommended stack + alternatives
  → Gather intake (or accept "recommended" / "defaults")
  → Write project-overview + project.yaml (init-project)
  → Discovery/plan (enterprise idea → … → task-breakdown)
  → MVP slices: each slice = plan→implement→commit→verify→review
  → Repeat until production checklist green

Stack presentation (parent)

  1. Show recommended stack with one-line why (from hook briefing).
  2. Show 1–2 alternatives.
  3. Ask intake questions OR accept defaults if user says recommended / just ship.

After stack locked

  1. Scaffold empty repo:
    • bash <pcore-orchestra>/scripts/init-project.sh . --type web --name "Notes App"
    • or powershell -File init-project.ps1
  2. Fill context/project-overview.md with MVP features + out-of-scope.
  3. Break into small vertical slices (one E2E feature per orchestra cycle).
  4. Run core loop per slice; commit before next phase.
  5. Research online only when templates lack guidance (one targeted search).

Production checklist (stop when all pass)

  • [ ] Auth works if required
  • [ ] Core MVP features demoable
  • [ ] Tests + lint/health green
  • [ ] Deploy config present
  • [ ] README + progress-tracker updated
  • [ ] No secrets in repo
  • [ ] Phase commit gate clean

Rules

  • Never jump to implementer before stack + MVP locked
  • Prefer recommended pcore stacks (Next/Hono/Prisma) unless user overrides
  • Prefer Context7 / six-file / templates over broad web search
  • One slice per cycle — no mega-PRs

04 同仓库更多 Skills

P-Core-System
P-Core-System/pcore-orchestra

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

web-perf

Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

web-design-master

Professional web design standard ("AI Professional Web Design Master Prompt") covering page/section/layout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

verification-before-completion

Require command evidence before claiming done. Use proactively before VERIFY_PASS, ORCHESTRA_COMPLETE, or "all fixed" statements. Run tests, lint, health, or git checks — never trust claims without output.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

ui-ux-pro-max

UI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML/CSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.

★ 0