Commit Graph

3 Commits

Author SHA1 Message Date
The Chronicler
5a7c8581dd Add FFG-STD-003: AI Portrait Generation Standard
Comprehensive guidelines for creating Chronicler portraits and AI artwork:
- Visual style: Illustrated/stylized (NOT photorealistic)
- Complete prompt structure template (12 required sections)
- Color palette guidelines (Firefrost blues, Fire/Frost balance)
- Technical specs (16:9 landscape, composition rules)
- Quality checklist for generated images
- Common mistakes to avoid
- Examples from Guardian, Builder, Architect

Why this standard:
- Ensures consistent visual style across all portraits
- Prevents photorealistic renders (generic/corporate)
- Maintains Fire/Frost brand aesthetic
- Provides repeatable process for future Chroniclers

Version: 1.0
Created by: The Analyst
2026-02-16 15:03:21 +00:00
d0b84e3a80 Fix task standard references to match reality
Per fresh Claude review feedback:
"Standard references examples that don't exist:
- docs/tasks/whitelist-manager/ (NOW EXISTS)
- docs/tasks/frostwall-protocol/ (doesn't exist)
- docs/tasks/mailcow-email/ (doesn't exist)
- docs/standards/git-workflow.md (doesn't exist)
- docs/standards/naming-conventions.md (doesn't exist)
- docs/standards/code-style.md (doesn't exist)"

FIXES:
1. Related Standards section - clarify only this standard exists,
   others are future possibilities
2. Example Task Directories - mark whitelist-manager as  IMPLEMENTED,
   others as examples for future tasks
3. Added "Note" sections to prevent confusion

Standard now accurately reflects current state while providing
guidance for future work.

Phase 6 of complete restructure.

Date: February 16, 2026
Implemented by: The Chronicler
2026-02-16 06:23:07 -06:00
446d525dea Add Task Documentation Standard (FFG-STD-002)
Establishes systematic approach to task documentation:

PROBLEM SOLVED:
- Tasks.md becoming unwieldy with mixed detail levels
- Implementation details buried in master task list
- Hard to find related documentation
- Duplication and sync issues
- Context muddying

SOLUTION:
- Each task gets dedicated directory in docs/tasks/
- Tasks.md stays high-level (executive summary only)
- Clear separation: planning vs implementation vs operations
- Scalable structure (1 to 20 docs per task)

STRUCTURE:
docs/tasks/[task-name]/
  ├── README.md (required - overview)
  ├── deployment-plan.md (if building)
  ├── usage-guide.md (if tool/service)
  ├── troubleshooting.md (if operational)
  ├── maintenance.md (ongoing ops)
  └── config-examples/ (as needed)

APPLICATION:
- All NEW tasks follow this pattern immediately
- Existing tasks migrate gradually (when touched)
- No breaking changes to existing docs

BENEFITS:
- Discoverable (all task docs in one place)
- Maintainable (update one location)
- Scalable (50+ tasks, tasks.md stays readable)
- Collaborative (clear where to look)

FIRST TASK USING STANDARD:
- Whitelist Manager (docs/tasks/whitelist-manager/)

Created by: The Chronicler
Date: February 16, 2026
Standard ID: FFG-STD-002
2026-02-16 05:50:38 -06:00