This plan outlines the process for extracting key topics from the 50-page DevelopersGuide.adoc and generating succinct, LLM-friendly markdown files for each topic. Each file will be verified against the actual source code for correctness.
Use Claude CLI with fresh sessions - Each topic will be processed in a separate Claude session using:
claude --session-id ai-docs-<topic-name> --print < topic-prompt.md
Or for resuming:
claude --session-id ai-docs-<topic-name> --resume
Verification Strategy - Each generated doc must:
src/main/com/fulcrologic/rad/Priority: Data Model - Special emphasis on RAD's attribute-centric model:
defattr macro)File: 01-attributes-data-model.md
Source sections: Lines 168-594 (Attribute-Centric, Attributes chapter)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-attributes-model
File: 02-relationships-cardinality.md
Source sections: Lines 473-545 (Referential Attributes, Attribute Types)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-relationships
File: 03-attribute-options.md
Source sections: Lines 495-588 (Attribute Types and Details, All Attributes)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-attr-options
File: 04-forms-basics.md
Source sections: Lines 1094-1181 (Forms), 273-284 (Forms intro)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-forms-basic
File: 05-form-relationships.md
Source sections: Lines 1331-1551 (Relationship Lifecycle)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-form-relationships
File: 06-form-validation.md
Source sections: Lines 1182-1258 (UI Validation)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-form-validation
File: 07-dynamic-forms.md
Source sections: Lines 1552-1700 (Dynamic Forms)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-dynamic-forms
File: 08-reports-basics.md
Source sections: Lines 3012-3148 (Reports), 285-313 (Reports intro)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-reports-basic
File: 09-report-rendering.md
Source sections: Lines 3149-3433 (Report Performance, Rendering)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-report-rendering
File: 10-server-setup.md
Source sections: Lines 604-798 (Server Setup)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-server-setup
File: 11-database-adapters.md
Source sections: Lines 871-987 (Database Adapters)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-db-adapters
File: 12-client-setup.md
Source sections: Lines 824-870 (Client Setup), 1130-1181 (Complete Client)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-client-setup
File: 13-custom-rendering.md
Source sections: Lines 988-1093 (Rendering Plugins), 2746-2891 (Custom Fields)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-custom-rendering
File: 14-file-upload.md
Source sections: Lines 1866-2120 (File Upload/Download)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-file-upload
File: 15-type-support.md
Source sections: Lines 1701-1865 (Extended Data Type Support)
Key areas:
Status: NOT STARTED
Session ID: ai-docs-type-support
For each topic, use this template as the basis for the extraction prompt:
# Topic Extraction Prompt for: <TOPIC_NAME>
## Context
You are extracting documentation from the Fulcro RAD Developer's Guide to create a succinct, LLM-friendly markdown file.
## Task
1. Read the specified sections from /workspace/docs/DevelopersGuide.adoc (lines <START>-<END>)
2. Extract the key concepts, examples, and explanations
3. Verify all code examples against actual source in /workspace/src/main/com/fulcrologic/rad/
4. Create a concise markdown file (200-500 lines target) at /workspace/docs/ai/<FILENAME>.md
## Requirements
- **Accuracy**: All code examples must be verified against source
- **Completeness**: Cover all major aspects of the topic
- **Conciseness**: Remove verbosity while preserving essential information
- **Examples**: Include practical, working code examples
- **References**: Note source file locations (e.g., attributes.cljc:89)
## Verification Strategy
- Use Read tool to examine source files mentioned in the guide
- Cross-reference attribute options with attributes-options namespace
- Ensure macro signatures match actual definitions
- Validate example code structure
## Topic-Specific Focus
<TOPIC_SPECIFIC_INSTRUCTIONS>
## Output Format
Create a markdown file with:
1. Title and brief overview (2-3 sentences)
2. Core concepts (with code examples)
3. Common patterns
4. Gotchas/important notes
5. Related topics (cross-references)
6. Source references
## Success Criteria
- Can an LLM use this doc to correctly implement the feature?
- Is the information dense but clear?
- Are all examples correct and runnable?
- Is it under 500 lines?
Phase 1: Data Model Foundation (DO FIRST)
Phase 2: Core Features
Phase 3: Advanced Features
Phase 4: Specialized Topics
# Create topic-specific prompt file
cat > /tmp/topic-prompt.md << 'EOF'
<paste template with topic-specific values>
EOF
# Run in fresh session
claude --session-id ai-docs-<topic> --print < /tmp/topic-prompt.md
claude --session-id ai-docs-<topic> --resume
# Check file was created
ls -lh docs/ai/<filename>.md
# Quick content check
head -50 docs/ai/<filename>.md
Update this section as topics are completed:
Total Generated: 13/15 topics (87% complete), 8170 lines, 304KB
(Add notes here as generation progresses)
Created: 2025-11-13 Last Updated: 2025-11-13 Status: COMPLETE - 13/15 topics generated (87%), 8170 lines, 304KB total. Skipped 2 advanced rendering topics (09, 13).
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |