fiddlerwoaroof/improvise
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: use Prolog as a design tool, not only a work log

Browse Source 
Author's own guidance, added during the session.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V69PGQfMJuGRmtSWpfVAqn
This commit is contained in:
Edward Langley
2026-08-29 12:31:06 -07:00
parent f47decffdd
commit c2a8d2710d
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+2
View File
@@ -12,6 +12,8 @@
every session and save structured facts to the knowledge base as you go. (cover work done, interesting
locations in the codebase, important decisions, etc.)
- query the knowledge base as needed and use Prolog reasoning when it makes sense.
- Prolog should be used as a design tool to reason about the code and the implementation of tickets and to
persist a formal model of it.
# Agent Instructions