a66996ac10
Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on 2026-10-01. Deliberately orphaned: prior history contained a plaintext password and stays local-only on branch archive/pre-boilerplate-history. Secrets and live Hermes state are gitignored.
47 lines
No EOL
1.8 KiB
Markdown
47 lines
No EOL
1.8 KiB
Markdown
Prompt Kyles Boilerplate Orion
|
||
|
||
```
|
||
Use this GitHub repository as the source of truth:
|
||
|
||
https://github.com/kyleisuncool/orion-boilerplate
|
||
|
||
I want my current repository configured to follow the boilerplate’s conventions and all applicable instructions.
|
||
|
||
First, inspect the repository yourself. Find and read all relevant instruction and configuration files, including—but not limited to:
|
||
|
||
- README.md
|
||
- CONTRIBUTING.md
|
||
- AGENTS.md
|
||
- CLAUDE.md
|
||
- GEMINI.md
|
||
- .github/ instructions and workflows
|
||
- package.json or equivalent project manifests
|
||
- Makefile, Taskfile, justfile, or setup scripts
|
||
- .editorconfig
|
||
- .gitignore and .gitattributes
|
||
- linting, formatting, testing, pre-commit, and CI configuration
|
||
- any nested instruction files in subdirectories
|
||
|
||
Treat more-specific instructions in nested directories as taking precedence over general instructions. Follow the instructions you discover rather than inventing replacements.
|
||
|
||
Compare those requirements with my current repository and create a migration plan. The plan should identify:
|
||
|
||
1. Which files need to be copied, adapted, or created
|
||
2. Which commands and scripts I should use
|
||
3. Which Git settings are repository-specific versus global
|
||
4. Any dependencies or tools I need to install
|
||
5. Any conflicts with my current setup
|
||
6. Any potentially destructive actions
|
||
|
||
Do not make changes yet. Do not:
|
||
- Delete files
|
||
- Rewrite Git history
|
||
- Reset branches
|
||
- Force-push
|
||
- Change my Git username, email, remotes, SSH keys, or credentials
|
||
- Copy secrets, API keys, private keys, or .env files
|
||
- Overwrite existing configuration without explaining the difference
|
||
|
||
After presenting the plan, wait for my approval. Once approved, give me exact commands in small, reversible steps and verify each step. Preserve my existing source code and uncommitted work.
|
||
|
||
``` |