Skip to content

Vertical Project Scaffolding Prompts

Six prompts targeting developers who spin up new CTO/CONSTEL-pattern vertical projects using fcc scaffold-vertical-project introduced in v1.3.0. The generator ships with 10 constellation-codename reference projects (Ophiuchus, Serpens, Libra, Crater, Scutum, Norma, Pyxis, Vela, Columba, Caelum).

Personas Used

Persona ID Full Name Category Role in Prompts
ASC Automation Scripter devops Generator invocation, CI wiring
ISP Integration Specialist integration Vocabulary contracts, extras
CS Content Strategist docs_as_code Seed data, docs scaffolding

Prompt 1: First scaffold-vertical-project Run

Audience: Developer Difficulty: beginner Personas: ASC

Context

A developer wants to produce a new vertical project for "maritime logistics."

Prompt

Walk through running:

    fcc scaffold-vertical-project \
      --codename "Carina" \
      --domain "maritime logistics" \
      --output ./carina

Confirm:
- The generated tree mirrors the CONSTEL pattern (src/, tests/,
  docs/, charts/, notebooks/)
- `pyproject.toml` declares the `[fcc-integration]` extras
- A starter persona pack is placed under `src/carina/personas/`
- CI workflows include the coverage ratchet

Produce a README snippet explaining what to do in the first hour,
and identify the one file most new contributors get wrong on their
first commit.

Expected Output

  • Command transcript
  • README snippet
  • Gotcha note

Prompt 2: Customizing the Jinja2 Templates

Audience: Developer Difficulty: intermediate Personas: ASC, CS

Prompt

The team wants every new scaffolded project to include a "research
journal" directory with a pre-populated `INDEX.md` and a weekly-log
template. Modify the Jinja2 templates under
`src/fcc/templates/project/` so that this directory is emitted on
every scaffold. Include (a) the template changes, (b) the new
context variables (if any), (c) a regression test that runs the
scaffold generator and asserts the directory exists.

Expected Output

  • Template diff
  • Test snippet

Prompt 3: Seed Data Authoring (Canonical 10 + Pattern Expansion)

Audience: Developer Difficulty: advanced Personas: CS, ISP

Prompt

Author a canonical 10-entity seed dataset for a "commercial real
estate" vertical (tenants, leases, properties, ...). Then define
three expansion patterns (geographic clone, time-series clone,
tier-variance) that together expand the baseline to exactly 500
entities with realistic variance.

Deliverables:
- `seed/canonical.yaml` (10 entities)
- `seed/patterns.yaml` (3 named patterns)
- A `scripts/expand_seed.py` that deterministically produces the 500

Critique: list two traps (id collisions, referential integrity) and
how the expansion script guards against them.

Expected Output

  • Three seed artifacts
  • Trap-and-guard commentary

Prompt 4: Vocabulary Contract Wiring

Audience: Developer Difficulty: intermediate Personas: ISP

Prompt

Wire a freshly scaffolded project to consume FCC's packaged YAML
mappings via a VocabularyProviderPlugin. Produce:
- The plugin manifest entry under the new project's
  `plugins/fcc_vocabulary.py`
- A bootstrap test that imports the provider, lists 3 terms, and
  resolves one
- The `[fcc-integration]` extras line in `pyproject.toml`

Explain why this avoids direct runtime imports from FCC and how the
arrangement survives FCC minor-version upgrades.

Expected Output

  • Plugin source
  • Bootstrap test
  • Upgrade-safety note

Prompt 5: [fcc-integration] Extras Audit

Audience: Developer Difficulty: intermediate Personas: ASC, ISP

Prompt

Audit the 10 shipped constellation projects and produce a table
showing which currently declare the `[fcc-integration]` extras,
which pin a compatible FCC version, and which are missing the
VocabularyProviderPlugin wiring. Propose a one-PR fix that brings
the laggards up to the v1.3.0 contract.

Expected Output

  • Audit table
  • One-PR plan

Prompt 6: Generator Smoke Test in CI

Audience: Developer Difficulty: intermediate Personas: ASC

Prompt

Write a GitHub Actions job that runs `fcc scaffold-vertical-project`
for a throwaway codename, installs the result in a fresh venv, runs
its pytest suite, and posts a comment on the triggering PR if the
smoke run fails. Use matrix to exercise Python 3.11 and 3.12.

Expected Output

  • Actions job YAML

See Also

  • src/fcc/templates/project/
  • v1.3.0 release notes
  • docs/tutorials/sample-prompts/scaffold-cli-prompts.md (if present)