Files
storkit/.living_spec/specs
Dave 990441dfc1 feat: Story 8 - Collapsible tool outputs + autonomous coding improvements
Implemented Story 8: Collapsible Tool Outputs
- Tool outputs now render in <details>/<summary> elements, collapsed by default
- Summary shows tool name with key argument (e.g., ▶ read_file(src/main.rs))
- Added arrow rotation animation and scrollable content (max 300px)
- Enhanced tool_calls display to show arguments inline
- Added CSS styling for dark theme consistency

Fixed: LLM autonomous coding behavior
- Strengthened system prompt with explicit examples and directives
- Implemented triple-reinforcement system (primary prompt + reminder + message prefixes)
- Improved tool descriptions to be more explicit and action-oriented
- Increased MAX_TURNS from 10 to 30 for complex agentic workflows
- Added debug logging for Ollama requests/responses
- Result: GPT-OSS (gpt-oss:20b) now successfully uses write_file autonomously

Documentation improvements
- Created MODEL_SELECTION.md guide with recommendations
- Updated PERSONA.md spec to emphasize autonomous agent behavior
- Updated UI_UX.md spec with collapsible tool output requirements
- Updated SDSW workflow: LLM archives stories and performs squash merge

Cleanup
- Removed unused ToolTester.tsx component
2025-12-25 15:18:12 +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.