claude-timemachine
c14d251142
Five skills copied for Jerry to study how Anthropic structures task-specific guidance for a coding agent. Not Jerry's own skills — examples of the pattern. mermaid/ Anthropic built-in; 18+ diagram types with on-demand references/ caveman/ Plugin: compressed communication mode (3 intensity levels) caveman-commit/ Plugin: conventional-commit message generation caveman-review/ Plugin: compressed PR review comments compress/ Plugin: memory-file compression The worth-borrowing pattern: every SKILL.md has a trigger line, rules, worked examples, and boundaries. Mermaid extends with references/ loaded on demand — the same shape would suit Jerry's code-review work (one SKILL.md plus per-topic references like go-concurrency.md, auth.md). README in the directory explains the layout and how Jerry can use these. — Claude Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
73 lines
2.2 KiB
Markdown
73 lines
2.2 KiB
Markdown
> **Warning**
|
|
>
|
|
> ## THIS IS AN AUTOGENERATED FILE. DO NOT EDIT.
|
|
>
|
|
> ## Please edit the corresponding file in [/packages/mermaid/src/docs/config/configuration.md](../../packages/mermaid/src/docs/config/configuration.md).
|
|
|
|
# Configuration
|
|
|
|
When mermaid starts, configuration is extracted to determine a configuration to be used for a diagram. There are 3 sources for configuration:
|
|
|
|
- The default configuration
|
|
- Overrides at the site level are set by the initialize call, and will be applied to all diagrams in the site/app. The term for this is the **siteConfig**.
|
|
- Frontmatter (v10.5.0+) - diagram authors can update selected configuration parameters in the frontmatter of the diagram. These are applied to the render config.
|
|
- Directives (Deprecated by Frontmatter) - diagram authors can update selected configuration parameters directly in the diagram code via directives. These are applied to the render config.
|
|
|
|
**The render config** is configuration that is used when rendering by applying these configurations.
|
|
|
|
## Frontmatter config
|
|
|
|
The entire mermaid configuration (except the secure configs) can be overridden by the diagram author in the frontmatter of the diagram. The frontmatter is a YAML block at the top of the diagram.
|
|
|
|
```mermaid-example
|
|
---
|
|
title: Hello Title
|
|
config:
|
|
theme: base
|
|
themeVariables:
|
|
primaryColor: "#00ff00"
|
|
---
|
|
flowchart
|
|
Hello --> World
|
|
|
|
```
|
|
|
|
```mermaid
|
|
---
|
|
title: Hello Title
|
|
config:
|
|
theme: base
|
|
themeVariables:
|
|
primaryColor: "#00ff00"
|
|
---
|
|
flowchart
|
|
Hello --> World
|
|
|
|
```
|
|
|
|
## Theme configuration
|
|
|
|
## Starting mermaid
|
|
|
|
```mermaid-example
|
|
sequenceDiagram
|
|
Site->>mermaid: initialize
|
|
Site->>mermaid: content loaded
|
|
mermaid->>mermaidAPI: init
|
|
```
|
|
|
|
```mermaid
|
|
sequenceDiagram
|
|
Site->>mermaid: initialize
|
|
Site->>mermaid: content loaded
|
|
mermaid->>mermaidAPI: init
|
|
```
|
|
|
|
## Initialize
|
|
|
|
The initialize call is applied **only once**. It is called by the site integrator in order to override the default configuration at a site level.
|
|
|
|
## configApi.reset
|
|
|
|
This method resets the configuration for a diagram to the overall site configuration, which is the configuration provided by the site integrator. Before each rendering of a diagram, reset is called at the very beginning.
|