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.
95 lines
No EOL
3 KiB
Markdown
95 lines
No EOL
3 KiB
Markdown
cde#installimpeccable #imnpeccablehermes #impeccablestyles
|
||
|
||
|
||
Impeccable has a Hermes Agent integration, so the simplest setup is to install it from your project directory.
|
||
|
||
1. Open a terminal in your project:
|
||
|
||
bash
|
||
|
||
```
|
||
cd /path/to/your/project
|
||
```
|
||
|
||
2. Run the installer:
|
||
|
||
bash
|
||
|
||
```
|
||
npx impeccable install
|
||
```
|
||
|
||
Choose Hermes Agent when prompted, then choose whether to install it for:
|
||
|
||
- This project only — recommended initially
|
||
- All projects — useful if you want Impeccable available everywhere
|
||
|
||
The installer selects the appropriate build and creates the files/integrations supported by your coding agent. Impeccable explicitly lists Hermes Agent as a supported tool. [GitHub](https://github.com/)
|
||
|
||
3. Start Hermes in that project and initialize Impeccable:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable init
|
||
```
|
||
|
||
This inspects the existing project and establishes design context. It can create or use:
|
||
|
||
- `PRODUCT.md` — product purpose, users, and accessibility requirements
|
||
- `DESIGN.md` — colors, typography, spacing, components, and design rules
|
||
|
||
Those files let future Hermes sessions preserve the same visual system instead of redesigning each page independently. [GitHub](https://github.com/)
|
||
|
||
Then give Hermes a concrete task, for example:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable audit the current dashboard and fix the highest-impact visual and usability issues.
|
||
```
|
||
|
||
Useful commands include:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable polish the settings page/impeccable critique the landing page/impeccable typeset the dashboard for better hierarchy and readability/impeccable layout improve spacing and grouping without changing the brand/impeccable colorize the page using the existing design system/impeccable simplify the onboarding flow/impeccable document
|
||
```
|
||
|
||
The commands are intended to be used directly in the agent conversation, and `document` records the project’s visual system in `DESIGN.md`. [GitHub](https://github.com/)
|
||
|
||
If the normal installer does not recognize Hermes, try the shared skills installer:
|
||
|
||
bash
|
||
|
||
```
|
||
npx skills add pbakaus/impeccable
|
||
```
|
||
|
||
Then restart Hermes and try:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable init
|
||
```
|
||
|
||
For best results, give Hermes product context before asking for visual changes:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable polish the billing page.
|
||
Users are small-business owners reviewing their subscription.The primary goal is to make plan comparison and cancellation status immediately clear.Keep the existing brand colors and rounded-card component.Prioritize mobile usability and accessibility.Do not add gradients, unnecessary cards, decorative animations, or new dependencies.
|
||
```
|
||
|
||
A practical workflow is:
|
||
|
||
text
|
||
|
||
```
|
||
/impeccable init/impeccable audit the page/impeccable polish the highest-priority issues/impeccable document
|
||
```
|
||
|
||
Run `init` once at the beginning, use `audit` before large changes, and use `document` after the design system has stabilized. Since Hermes retains skills and project information between sessions, keeping `PRODUCT.md` and `DESIGN.md` in the repository helps it maintain continuity. [nousresearch.com](https://hermes-agent.nousresearch.com/) |