Files
g3/prompts/langs/racket.md
Dhanji R. Prasanna afec65fd50 Add language-specific prompt injection for toolchain guidance
- Add language_prompts module that auto-detects programming languages in workspace
- Scan for language files with depth limit (2) to inject relevant toolchain prompts
- Add prompts/langs/ directory for language-specific markdown files
- Include Racket/raco toolchain guidance as first language prompt
- Update combine_project_content() to accept language_content parameter
- Integrate language detection into main CLI flow and agent mode
- Update project memory with new feature documentation
2026-01-14 21:00:52 +05:30

31 lines
1.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
RACKET LANGUAGE CODE EXPLORATION + RACO TOOLING
- Core `raco` commands to rely on:
- Documentation & discovery:
- `raco docs <id>` to open docs for identifiers, modules, or packages.
- Compilation & checks:
- `raco make <file.rkt>` to force compilation and surface errors early.
- Testing:
- `raco test <path>` to run `module+ test` blocks and test files.
- Packages & dependencies:
- `raco pkg show` to inspect installed packages and their locations.
- `raco pkg show <pkg>` to inspect package metadata and versions.
- Profiling & performance:
- `raco profile <file.rkt>` for CPU hot spots.
- Debugging & stack traces:
- `racket -l errortrace <file.rkt>` (or enabling errortrace) for readable stack traces.
- Structural analysis tools (use when reasoning about non-trivial codebases):
- `raco dependency-graph <path>`:
- Use to visualize or reason about module dependencies and layering.
- Identify cycles, high fan-in “core” modules, and accidental coupling.
- `raco modgraph`:
- Use for quick textual inspection of module graphs when visualization isnt needed.
- Treat dependency graphs as architectural signals, not just diagrams.
- `racket -e`-driven exploration:
- Use the one-shot script execution to:
- `require` modules incrementally and inspect exports.
- Probe functions with small concrete examples.
- Validate assumptions about data shapes and return values.