Files
storkit/.living_spec/specs
Dave 0ff1a4b167 feat: Story 11 - Left-align text and add syntax highlighting
Implemented Story 11: Text Alignment and Syntax Highlighting
- Removed center-alignment from chat container (text-align: center)
- Added left-alignment to markdown body and code blocks
- Integrated react-syntax-highlighter with react-markdown
- Added syntax highlighting for code blocks using oneDark theme
- Supports JavaScript, TypeScript, Rust, Python, JSON, Markdown, Shell, and more
- Inline code maintains simple styling without full highlighting
- All code blocks are now left-aligned for better readability

Fixed: Agent over-aggressive file writing behavior
- Refined system prompt to distinguish between:
  * 'show/example/how does' → respond with code in chat
  * 'create/add/implement/fix' → use write_file tool
- Removed aggressive AGENT DIRECTIVE prefix from user messages
- Softened reminder message to reflect nuanced behavior
- Agent can now both teach (show examples) and implement (write files)

Updated Specs
- Added Text Alignment and Readability section to UI_UX.md
- Added Syntax Highlighting section with implementation details
- Updated SDSW workflow: acceptance criteria marked complete only after user acceptance

Dependencies
- Added react-syntax-highlighter and @types/react-syntax-highlighter
2025-12-25 15:39:22 +00:00
..
2025-12-24 16:29:33 +00:00
2025-12-24 16:29:33 +00:00

Project Specs

This folder contains the "Living Specification" for the project. It serves as the source of truth for all AI sessions.

Structure

  • 00_CONTEXT.md: The high-level overview, goals, domain definition, and glossary. Start here.
  • tech/: Implementation details, including the Tech Stack, Architecture, and Constraints.
    • STACK.md: The technical "Constitution" (Languages, Libraries, Patterns).
  • functional/: Domain logic and behavior descriptions, platform-agnostic.
    • 01_CORE.md: Core functional specifications.

Usage for LLMs

  1. Always read 00_CONTEXT.md and tech/STACK.md at the beginning of a session.
  2. Before writing code, ensure the spec in this folder reflects the desired reality.
  3. If a Story changes behavior, update the spec first, get approval, then write code.