wwwfiberdirekt/AGENTS-README.md

Fiber Direkt — Agent System (Updated)

Complete multi-agent system for building Fiber Direkt websites and campaigns via Claude Code. All reference files included — no external skills required.

What's Included

.claude/
├── agents/
│   ├── site-architect.md      — Page maps with block sequences + valid select values
│   ├── content-writer.md      — Swedish B2B copy with field-name validation
│   ├── image-director.md      — Nano Banana Pro prompts with proven prompt formula
│   ├── seed-script-builder.md — Payload CMS seed scripts with schema validation
│   ├── campaign-strategist.md — Campaign plans, calendars, carousel briefs
│   ├── carousel-builder.md    — LinkedIn carousel HTML files
│   └── linkedin-writer.md     — Ready-to-publish LinkedIn posts
├── commands/
│   ├── build-site.md          — Full site + campaign from brief
│   └── produce-campaign.md    — Campaign-only content package
references/
├── brand-voice.md             — Voice, tone, language rules, messaging pillars
├── products-services.md       — All products, pricing, specs, certifications
├── copy-examples.md           — Approved copy from existing landing pages
└── post-patterns.md           — LinkedIn post templates and format rules
templates/
├── brief-template.md          — The input document you fill in
└── example-brief-fiberdirekt.md — Filled-in example brief

Setup

Copy everything into your Fiber Direkt project root:

cd /path/to/wwwfiberdirekt

# Copy the directories
cp -r [download-path]/.claude/ ./.claude/
cp -r [download-path]/references/ ./references/
cp -r [download-path]/templates/ ./templates/

Your project should now have:

wwwfiberdirekt/
├── .claude/agents/...        ← agent definitions
├── .claude/commands/...      ← slash commands
├── references/...            ← brand + product knowledge
├── templates/...             ← brief template
├── src/...                   ← existing project code
├── CLAUDE.md                 ← existing conventions file
└── fiber-direkt-project-reference-Payload-cms2.md  ← block library reference

Important: The project reference file (fiber-direkt-project-reference-Payload-cms2.md) must be in the project root. Several agents read it for block schemas.

Prerequisites

• Claude Code installed and authenticated (Pro or Max subscription)
• Fiber Direkt project cloned locally
• No external skills needed — all reference files are included

Usage

Full Site Build

1. Copy templates/brief-template.md, fill it in
2. In Claude Code: /build-site templates/your-brief.md
3. Agents run in sequence, outputs appear in project root

Campaign Only

/produce-campaign "data sovereignty for Swedish enterprises"

Individual Agents

Use the site-architect agent to create a page map for this brief: [paste brief]
Use the content-writer agent to write copy for the colocation page
Use the linkedin-writer agent to write 4 weeks of posts from campaign-plan.md

What Changed from v1

1. Reference files created — references/ directory with brand voice, product specs, copy examples, and LinkedIn patterns. Agents now read actual files instead of referencing nonexistent skills.

2. Field-name validation — content-writer now warns about common field mismatches (fdHero uses theme not sectionBackground, fdPricingCard uses sectionTitle not heading). Seed-script-builder includes a critical field mapping table and runs node --check validation.

3. Valid select values — site-architect has a complete list of valid select values per block, preventing invalid configs that would break seed scripts.

4. Nano Banana Pro tips — image-director includes model-specific guidance and the proven prompt formula (subject → lighting rig → lens → depth of field → "Photorealistic.").

5. Simplified carousel builder — no longer depends on external fd-carousel skill. Produces self-contained HTML with inline CSS.

Maintenance

When you add new blocks or change pricing:

• Update fiber-direkt-project-reference-Payload-cms2.md for new blocks
• Update references/products-services.md for pricing changes
• Update references/brand-voice.md if tone/messaging shifts
• Agent definitions only need updating if the workflow itself changes

Cost Expectations

On Max $100/month plan, a full /build-site run uses roughly 150K–300K tokens across all agents. You can run several full builds per week without hitting caps. Individual agent calls are much lighter (~20K–40K tokens each).