holycodex 0.16.9-dev.103.1 → 0.16.9-dev.108.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -4
- package/dist/agent.js +55 -64
- package/dist/assets/plugin/plugin.json +1 -1
- package/dist/assets/plugin/skills/babysit-ci/SKILL.md +10 -3
- package/dist/assets/plugin/skills/babysit-ci/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/codebase-onboarding/SKILL.md +1 -1
- package/dist/assets/plugin/skills/codebase-onboarding/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/commit/SKILL.md +1 -1
- package/dist/assets/plugin/skills/commit/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/compress/SKILL.md +1 -1
- package/dist/assets/plugin/skills/compress/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/context7-cli/SKILL.md +1 -1
- package/dist/assets/plugin/skills/context7-cli/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/continue-work/SKILL.md +1 -1
- package/dist/assets/plugin/skills/continue-work/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/debugging/SKILL.md +1 -1
- package/dist/assets/plugin/skills/debugging/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/dev-server/SKILL.md +13 -0
- package/dist/assets/plugin/skills/dev-server/agents/openai.yaml +6 -0
- package/dist/assets/plugin/skills/grill-me/SKILL.md +9 -9
- package/dist/assets/plugin/skills/grill-me/agents/openai.yaml +2 -2
- package/dist/assets/plugin/skills/handoff/SKILL.md +1 -1
- package/dist/assets/plugin/skills/handoff/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/refactor/SKILL.md +1 -1
- package/dist/assets/plugin/skills/refactor/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/rules/SKILL.md +1 -1
- package/dist/assets/plugin/skills/rules/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/stop-slop/SKILL.md +4 -2
- package/dist/assets/plugin/skills/stop-slop/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/stop-slop/references/examples.md +9 -63
- package/dist/assets/plugin/skills/stop-slop/references/phrases.md +4 -3
- package/dist/assets/plugin/skills/stop-slop/references/structures.md +10 -131
- package/dist/assets/plugin/skills/visual-loop/SKILL.md +17 -0
- package/dist/assets/plugin/skills/visual-loop/agents/openai.yaml +6 -0
- package/dist/assets/plugin/skills/web-visualize/SKILL.md +4 -5
- package/dist/assets/plugin/skills/web-visualize/agents/openai.yaml +1 -1
- package/dist/assets/plugin/skills/writing-instructions/SKILL.md +31 -40
- package/dist/assets/plugin/skills/writing-instructions/agents/openai.yaml +1 -1
- package/dist/index.js +55 -51
- package/package.json +2 -2
- package/dist/assets/plugin/skills/code-review/SKILL.md +0 -8
- package/dist/assets/plugin/skills/code-review/agents/openai.yaml +0 -6
- package/dist/assets/plugin/skills/operations/SKILL.md +0 -10
- package/dist/assets/plugin/skills/operations/agents/openai.yaml +0 -6
- package/dist/assets/plugin/skills/plan/SKILL.md +0 -10
- package/dist/assets/plugin/skills/plan/agents/openai.yaml +0 -6
- package/dist/assets/plugin/skills/plan-review/SKILL.md +0 -7
- package/dist/assets/plugin/skills/plan-review/agents/openai.yaml +0 -6
- package/dist/assets/plugin/skills/programming/SKILL.md +0 -7
- package/dist/assets/plugin/skills/programming/agents/openai.yaml +0 -6
- package/dist/assets/plugin/skills/writing-instructions/SKILL-MECHANICS.md +0 -16
|
@@ -1,10 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: babysit-ci
|
|
3
|
-
description: Use when
|
|
3
|
+
description: Use when CI or release gates need follow-through; monitor their terminal results and report gate evidence.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Babysit CI
|
|
7
7
|
|
|
8
|
+
Root owns orchestration and mutations; Worker.operations observes the assigned
|
|
9
|
+
gates. Dispatch independent checks and review observation concurrently.
|
|
10
|
+
Use only the gates in the user's requested scope. When asked to monitor CI
|
|
11
|
+
only or ignore review bots, omit review observation and review findings.
|
|
12
|
+
|
|
8
13
|
Discover the repository's development and release topology for pushes and pull
|
|
9
14
|
requests: refs, required checks, reviews, publication mechanism, and gate
|
|
10
15
|
dependencies. Do not assume a provider, branch name, or separate pipeline.
|
|
@@ -13,13 +18,15 @@ For a push, bind every observation to the exact pushed ref and SHA. For a pull
|
|
|
13
18
|
request, bind it to the current head SHA, target branch, pull-request identity,
|
|
14
19
|
and review commit when the provider exposes one. Inspect required checks and
|
|
15
20
|
relevant bot reviews, inline threads, issue comments, and commit comments. A
|
|
16
|
-
new push
|
|
17
|
-
|
|
21
|
+
new push requires CI and review evidence for the new head; reuse unchanged
|
|
22
|
+
topology and local proof that remains applicable.
|
|
18
23
|
|
|
19
24
|
Use bounded observer waits. Distinguish a bot that is absent or not configured
|
|
20
25
|
from a known bot with no terminal signal, and both from a clean terminal
|
|
21
26
|
disposition. Absence or no signal is an evidence gap. Green checks do not
|
|
22
27
|
resolve outstanding review findings or threads.
|
|
28
|
+
Include target-branch or pull-request mergeability evidence when exposed;
|
|
29
|
+
green checks alone do not prove mergeability.
|
|
23
30
|
|
|
24
31
|
After a development action, observe its exact ref and SHA to terminal state.
|
|
25
32
|
Repair failed checks and actionable review findings, then repeat validation and
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Babysit CI"
|
|
3
3
|
short_description: "Follow repository CI and release gates to completion."
|
|
4
|
-
default_prompt: "Use babysit-ci for this
|
|
4
|
+
default_prompt: "Use $babysit-ci for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: codebase-onboarding
|
|
3
|
-
description: Use when
|
|
3
|
+
description: Use when someone needs a repository explanation or contributor orientation; summarize its purpose, structure, and workflows from evidence.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Provide a bounded, read-only orientation to the current repository or answer a
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Codebase onboarding"
|
|
3
3
|
short_description: "Explain a repository from a bounded read-only map."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $codebase-onboarding for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: commit
|
|
3
|
-
description: Use when Root
|
|
3
|
+
description: Use when Root is ready to commit settled and verified work; create the smallest coherent commits that follow repository conventions.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
After scope and proof are settled, follow the repository's commit conventions
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Commit"
|
|
3
3
|
short_description: "Create coherent local commits with exact scope proof."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $commit for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: false
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: compress
|
|
3
|
-
description: Use when assigned text must be shortened without changing its contract or voice.
|
|
3
|
+
description: Use when assigned text must be shortened without changing its contract or voice; preserve meaning and constraints in a more concise version.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Shorten only the assigned text. Preserve meaning, constraints, technical terms,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Compress"
|
|
3
3
|
short_description: "Shorten assigned text without changing its contract or voice."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $compress for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: context7-cli
|
|
3
|
-
description: Use when
|
|
3
|
+
description: Use when current technical documentation is needed through Context7 CLI; find the requested version-specific facts.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Resolve the requested library identity with the installed ctx7 CLI, then query
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Context7 CLI"
|
|
3
3
|
short_description: "Find assigned current library and API documentation first."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $context7-cli for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: false
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: continue-work
|
|
3
|
-
description: Use when the user asks Root to continue
|
|
3
|
+
description: Use when the user asks Root to continue existing HolyCodex work; restore its current state and carry unresolved work forward.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Restore the current Intent, Plan if present, Assignments, accepted evidence,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Continue work"
|
|
3
3
|
short_description: "Resume the current HolyCodex work from durable state."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $continue-work for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: debugging
|
|
3
|
-
description: Use
|
|
3
|
+
description: Use when an observable defect or unexplained behavior needs diagnosis; establish its cause and repair it within the assigned boundary.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Reproduce the issue with the smallest useful case when practical; otherwise,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Debugging"
|
|
3
3
|
short_description: "Diagnose an observable defect through reproduction or strong evidence."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $debugging for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: false
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: dev-server
|
|
3
|
+
description: Use when a shared background development server is needed; let Root start, reuse, and manage one server for the session.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Root only. Reuse a healthy server for the current project; otherwise start the
|
|
7
|
+
repository's development command in the background using the active runtime's
|
|
8
|
+
process controls. Confirm readiness, return its URL, and share the URL with
|
|
9
|
+
specialists so they reuse it. Root retains the process handle. Keep it alive
|
|
10
|
+
across Assignments; restart only when configuration or server state requires
|
|
11
|
+
it. Stop only the process owned by this session when
|
|
12
|
+
no longer needed. Specialists request server changes through their terminal
|
|
13
|
+
report rather than starting competing servers.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: grill-me
|
|
3
|
-
description: Use when
|
|
3
|
+
description: Use when Root needs an outcome-changing user decision; ask focused questions while independent work continues.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Grill me
|
|
@@ -10,12 +10,12 @@ behavior, UX, compatibility, dependencies, cost, security, external effects,
|
|
|
10
10
|
or another meaningful user-visible result. Infer obvious safe defaults and
|
|
11
11
|
continue without questioning routine omissions.
|
|
12
12
|
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
13
|
+
Root only. Ask the smallest set of questions needed for the blocked decision,
|
|
14
|
+
in waves and in the user's language, using existing evidence and authorization.
|
|
15
|
+
Never ask what is already known. If no material questions remain, orchestrate
|
|
16
|
+
immediately. Continue independent authorized
|
|
17
|
+
work while awaiting the answer. Do not delay a necessary question for a
|
|
18
|
+
discovery ritual or ask about hypothetical later phases.
|
|
18
19
|
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
unblocked; use `needs_root_input` when the choice remains unresolved.
|
|
20
|
+
Record the decision in current Intent evidence. Use `needs_root_input` only
|
|
21
|
+
when the missing answer prevents further progress.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Grill me"
|
|
3
3
|
short_description: "Ask only material, dependency-ordered clarification questions."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $grill-me for this task."
|
|
5
5
|
policy:
|
|
6
|
-
allow_implicit_invocation:
|
|
6
|
+
allow_implicit_invocation: false
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: handoff
|
|
3
|
-
description: Use when
|
|
3
|
+
description: Use when current Intent state must be resumed or exported; produce a compact redacted status projection with evidence and next action.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Produce one compact projection of current Intent, Plan, and Assignment status,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Handoff"
|
|
3
3
|
short_description: "Export a redacted projection of current Intent state."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $handoff for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: false
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: refactor
|
|
3
|
-
description: Use when one decided seam needs restructuring
|
|
3
|
+
description: Use when one decided seam needs restructuring without behavior or interface changes; refactor that seam and verify its boundaries.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Restructure only the decided seam. Trace callers before changing a shared root
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Refactor"
|
|
3
3
|
short_description: "Restructure one decided seam while preserving its contract."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $refactor for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: rules
|
|
3
|
-
description: Use when a repository rule needs discovery, validation, or diagnosis
|
|
3
|
+
description: Use when a repository rule needs discovery, validation, or failure diagnosis; trace its owner and report the rule with evidence.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Trace the owning rule loader and its limits, caching, trust boundary, and
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Rules"
|
|
3
3
|
short_description: "Trace one repository rule discovery or application failure."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $rules for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: false
|
|
@@ -1,9 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: stop-slop
|
|
3
|
-
description: Use when assigned prose
|
|
3
|
+
description: Use when assigned prose has predictable AI writing patterns; remove them while preserving meaning and voice.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Edit only the assigned prose. Remove filler, formulaic structure, vague claims,
|
|
7
|
-
passive voice, and repeated rhythm while preserving meaning and voice.
|
|
7
|
+
unnecessary passive voice, and repeated rhythm while preserving meaning and voice.
|
|
8
|
+
Treat reference examples as candidates, not bans on ordinary grammar. Preserve
|
|
9
|
+
qualifiers, uncertainty, factual distinctions, and technical precision. Use the
|
|
8
10
|
linked [phrase](references/phrases.md), [structure](references/structures.md),
|
|
9
11
|
and [example](references/examples.md) references when needed.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Stop Slop"
|
|
3
3
|
short_description: "Edit assigned prose to remove predictable AI patterns."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $stop-slop for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|
|
@@ -1,69 +1,15 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Examples
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Before: "It turns out that most teams struggle with alignment. The uncomfortable
|
|
4
|
+
truth is that nobody wants to admit they're confused. And that's okay."
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
After: "Most teams struggle with alignment. People may hesitate to admit confusion."
|
|
6
7
|
|
|
7
|
-
|
|
8
|
+
Remove the framing while retaining the qualification and uncertainty.
|
|
8
9
|
|
|
9
|
-
|
|
10
|
+
Before: "In today's fast-paced landscape, we need to lean into discomfort and
|
|
11
|
+
navigate uncertainty with clarity. This matters because your competition isn't waiting."
|
|
10
12
|
|
|
11
|
-
|
|
13
|
+
After: "We need to handle uncertainty clearly and keep pace with competitors."
|
|
12
14
|
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## Example 2: Filler + Unnecessary Reassurance
|
|
18
|
-
|
|
19
|
-
**Before:**
|
|
20
|
-
|
|
21
|
-
> "It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay."
|
|
22
|
-
|
|
23
|
-
**After:**
|
|
24
|
-
|
|
25
|
-
> "Teams struggle with alignment. Nobody admits confusion."
|
|
26
|
-
|
|
27
|
-
**Changes:** Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.
|
|
28
|
-
|
|
29
|
-
---
|
|
30
|
-
|
|
31
|
-
## Example 3: Business Jargon Stack
|
|
32
|
-
|
|
33
|
-
**Before:**
|
|
34
|
-
|
|
35
|
-
> "In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity. This matters because your competition isn't waiting."
|
|
36
|
-
|
|
37
|
-
**After:**
|
|
38
|
-
|
|
39
|
-
> "Move faster. Your competition is."
|
|
40
|
-
|
|
41
|
-
**Changes:** Eliminated jargon entirely. Core message in six words.
|
|
42
|
-
|
|
43
|
-
---
|
|
44
|
-
|
|
45
|
-
## Example 4: Dramatic Fragmentation
|
|
46
|
-
|
|
47
|
-
**Before:**
|
|
48
|
-
|
|
49
|
-
> "Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."
|
|
50
|
-
|
|
51
|
-
**After:**
|
|
52
|
-
|
|
53
|
-
> "Speed, quality, cost—pick two."
|
|
54
|
-
|
|
55
|
-
**Changes:** Single sentence. No performative emphasis.
|
|
56
|
-
|
|
57
|
-
---
|
|
58
|
-
|
|
59
|
-
## Example 5: Rhetorical Setup
|
|
60
|
-
|
|
61
|
-
**Before:**
|
|
62
|
-
|
|
63
|
-
> "What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning. Think about it."
|
|
64
|
-
|
|
65
|
-
**After:**
|
|
66
|
-
|
|
67
|
-
> "The best teams optimize for learning, not productivity."
|
|
68
|
-
|
|
69
|
-
**Changes:** Direct claim. No rhetorical scaffolding.
|
|
15
|
+
Replace jargon without dropping the original requirement or inventing a new claim.
|
|
@@ -20,11 +20,11 @@ Remove these announcement phrases. State the content directly.
|
|
|
20
20
|
- "Here's what I find interesting"
|
|
21
21
|
- "Here's the problem though"
|
|
22
22
|
|
|
23
|
-
|
|
23
|
+
Cut an opener when it adds no information.
|
|
24
24
|
|
|
25
25
|
## Emphasis Crutches
|
|
26
26
|
|
|
27
|
-
|
|
27
|
+
Delete these when they add no meaning.
|
|
28
28
|
|
|
29
29
|
- "Full stop." / "Period."
|
|
30
30
|
- "Let that sink in."
|
|
@@ -52,7 +52,8 @@ Replace with plain language.
|
|
|
52
52
|
|
|
53
53
|
## Adverbs
|
|
54
54
|
|
|
55
|
-
|
|
55
|
+
Remove empty intensifiers and redundant hedges. Keep adverbs and qualifiers
|
|
56
|
+
that convey degree, timing, uncertainty, or a technical distinction.
|
|
56
57
|
|
|
57
58
|
Specific offenders:
|
|
58
59
|
|
|
@@ -1,134 +1,13 @@
|
|
|
1
|
-
# Structures to
|
|
1
|
+
# Structures to reconsider
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Remove formulaic framing when it obscures the content: repeated binary contrasts,
|
|
4
|
+
rhetorical questions immediately answered, manufactured drama, and strings of
|
|
5
|
+
punchy fragments. State the concrete claim and its evidence.
|
|
4
6
|
|
|
5
|
-
|
|
7
|
+
Name the actor when it matters. Use active voice when clearer; passive voice is
|
|
8
|
+
useful when the actor is unknown or the object is the focus. Metaphors and ordinary
|
|
9
|
+
sentence openings are acceptable when they serve the assigned voice.
|
|
6
10
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
| "[X] isn't the problem. [Y] is." | Formulaic reframe |
|
|
11
|
-
| "The answer isn't X. It's Y." | Predictable pivot |
|
|
12
|
-
| "It feels like X. It's actually Y." | Setup/reveal cliche |
|
|
13
|
-
| "The question isn't X. It's Y." | Rhetorical misdirection |
|
|
14
|
-
| "Not X. But Y." / "not X, it's Y" / "isn't X, it's Y" | Mechanical contrast |
|
|
15
|
-
| "It's not this. It's that." | Same formula, different words |
|
|
16
|
-
| "stops being X and starts being Y" | False transformation arc |
|
|
17
|
-
| "doesn't mean X, but actually Y" | Negation-then-assertion crutch |
|
|
18
|
-
| "is about X but not Y" | False distinction |
|
|
19
|
-
| "not just X but also Y" | Additive hedge |
|
|
20
|
-
|
|
21
|
-
**Instead:** State Y directly. "The problem is Y." "Y matters here." Drop the negation entirely.
|
|
22
|
-
|
|
23
|
-
## Negative Listing
|
|
24
|
-
|
|
25
|
-
Listing what something is _not_ before revealing what it _is_. A rhetorical striptease.
|
|
26
|
-
|
|
27
|
-
| Pattern | Problem |
|
|
28
|
-
| ------------------------------------- | --------------------------------- |
|
|
29
|
-
| "Not a X... Not a Y... A Z." | Dramatic buildup through negation |
|
|
30
|
-
| "It wasn't X. It wasn't Y. It was Z." | Same structure, past tense |
|
|
31
|
-
|
|
32
|
-
**Instead:** State Z. The reader doesn't need the runway.
|
|
33
|
-
|
|
34
|
-
## Dramatic Fragmentation
|
|
35
|
-
|
|
36
|
-
Sentence fragments for emphasis read as manufactured profundity.
|
|
37
|
-
|
|
38
|
-
| Pattern | Problem |
|
|
39
|
-
| ---------------------------------------- | ----------------------- |
|
|
40
|
-
| "[Noun]. That's it. That's the [thing]." | Performative simplicity |
|
|
41
|
-
| "X. And Y. And Z." | Staccato drama |
|
|
42
|
-
| "This unlocks something. [Word]." | Artificial revelation |
|
|
43
|
-
|
|
44
|
-
**Instead:** Complete sentences. Trust content over presentation.
|
|
45
|
-
|
|
46
|
-
## Rhetorical Setups
|
|
47
|
-
|
|
48
|
-
These announce insight rather than deliver it.
|
|
49
|
-
|
|
50
|
-
| Pattern | Problem |
|
|
51
|
-
| --------------------- | ---------------------- |
|
|
52
|
-
| "What if [reframe]?" | Socratic posturing |
|
|
53
|
-
| "Here's what I mean:" | Redundant preview |
|
|
54
|
-
| "Think about it:" | Condescending prompt |
|
|
55
|
-
| "And that's okay." | Unnecessary permission |
|
|
56
|
-
|
|
57
|
-
**Instead:** Make the point. Let readers draw conclusions.
|
|
58
|
-
|
|
59
|
-
## Formulaic Constructions
|
|
60
|
-
|
|
61
|
-
| Pattern | Problem |
|
|
62
|
-
| ------------------------- | --------------------------- |
|
|
63
|
-
| "By the time X, I was Y." | Narrative template |
|
|
64
|
-
| "X that isn't Y" | Indirect. Say "X is broken" |
|
|
65
|
-
|
|
66
|
-
## False Agency
|
|
67
|
-
|
|
68
|
-
Giving inanimate things human verbs. Complaints don't "become" fixes. Bets don't "live or die." Decisions don't "emerge." A person does something to make those things happen. AI loves this because it avoids naming the actor.
|
|
69
|
-
|
|
70
|
-
| Pattern | Problem |
|
|
71
|
-
| ------------------------------- | ----------------------------------------------------------------- |
|
|
72
|
-
| "a complaint becomes a fix" | The complaint did nothing. Someone fixed it. |
|
|
73
|
-
| "a bet lives or dies in days" | Bets don't have lifespans. Someone kills the project or ships it. |
|
|
74
|
-
| "the decision emerges" | Decisions don't emerge. Someone decides. |
|
|
75
|
-
| "the culture shifts" | Cultures don't shift on their own. People change behavior. |
|
|
76
|
-
| "the conversation moves toward" | Conversations don't move. Someone steers. |
|
|
77
|
-
| "the data tells us" | Data sits there. Someone reads it and draws a conclusion. |
|
|
78
|
-
| "the market rewards" | Markets don't reward. Buyers pay for things. |
|
|
79
|
-
|
|
80
|
-
**Instead:** Name the human. "The team fixed it that week" beats "the complaint becomes a fix." If no specific person fits, use "you" to put the reader in the seat.
|
|
81
|
-
|
|
82
|
-
## Narrator-from-a-Distance
|
|
83
|
-
|
|
84
|
-
Floating above the scene instead of putting the reader in it.
|
|
85
|
-
|
|
86
|
-
| Pattern | Problem |
|
|
87
|
-
| ------------------------- | ----------------------- |
|
|
88
|
-
| "Nobody designed this." | Disembodied observation |
|
|
89
|
-
| "This happens because..." | Lecturer voice |
|
|
90
|
-
| "This is why..." | Same |
|
|
91
|
-
| "People tend to..." | Armchair sociologist |
|
|
92
|
-
|
|
93
|
-
**Instead:** Put the reader in the room. "You don't sit down one day and decide to..." beats "Nobody designed this."
|
|
94
|
-
|
|
95
|
-
## Passive Voice
|
|
96
|
-
|
|
97
|
-
Every sentence needs a subject doing something. Passive voice hides the actor and drains energy.
|
|
98
|
-
|
|
99
|
-
| Pattern | Fix |
|
|
100
|
-
| -------------------------- | -------------------- |
|
|
101
|
-
| "X was created" | Name who created it |
|
|
102
|
-
| "It is believed that" | Name who believes it |
|
|
103
|
-
| "Mistakes were made" | Name who made them |
|
|
104
|
-
| "The decision was reached" | Name who decided |
|
|
105
|
-
|
|
106
|
-
**Instead:** Find the actor. Put them at the front of the sentence.
|
|
107
|
-
|
|
108
|
-
## Sentence Starters to Avoid
|
|
109
|
-
|
|
110
|
-
| Pattern | Fix |
|
|
111
|
-
| --------------------------------------------------------------- | ----------------------------------------------- |
|
|
112
|
-
| Sentences starting with What, When, Where, Which, Who, Why, How | Restructure. Lead with the subject or the verb. |
|
|
113
|
-
| Paragraphs starting with "So" | Start with content |
|
|
114
|
-
| Sentences starting with "Look," | Remove |
|
|
115
|
-
|
|
116
|
-
Wh- openers become a crutch. "What makes this hard is..." becomes "The constraint is..." or better, name the specific constraint.
|
|
117
|
-
|
|
118
|
-
## Rhythm Patterns
|
|
119
|
-
|
|
120
|
-
| Pattern | Fix |
|
|
121
|
-
| ------------------------------ | --------------------------------------------------- |
|
|
122
|
-
| Three-item lists | Use two items or one |
|
|
123
|
-
| Questions answered immediately | Let questions breathe or cut them |
|
|
124
|
-
| Every paragraph ends punchily | Vary endings |
|
|
125
|
-
| Em-dashes | Remove. Use commas or periods. No em dashes at all. |
|
|
126
|
-
| Staccato fragmentation | Don't stack short punchy sentences |
|
|
127
|
-
| "Not always. Not perfectly." | Hedging disguised as reassurance |
|
|
128
|
-
|
|
129
|
-
## Word Patterns
|
|
130
|
-
|
|
131
|
-
| Pattern | Problem |
|
|
132
|
-
| ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
|
|
133
|
-
| Lazy extremes (every, always, never, everyone, everybody, nobody) | False authority. Use specifics instead of sweeping claims. |
|
|
134
|
-
| All adverbs (-ly words, "really," "just," "literally," "genuinely," "honestly," "simply," "actually") | Empty emphasis. See phrases.md for full list. |
|
|
11
|
+
Vary rhythm without arbitrary bans on punctuation, three-item lists, question
|
|
12
|
+
words, or adverbs. Preserve meaningful contrast, qualifications, uncertainty,
|
|
13
|
+
and technical precision. Judge the passage rather than matching forbidden forms.
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: visual-loop
|
|
3
|
+
description: Use when visual changes need rendered judgment; let Root inspect the current result and assign concrete repairs.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Root only, for visual tasks. Orchestrate implementation, inspect its rendered
|
|
7
|
+
result, judge the visual output, dispatch targeted changes to specialists, and
|
|
8
|
+
repeat until the result is excellent and meets the user's requirements.
|
|
9
|
+
|
|
10
|
+
Follow the visual-inspection order generated for Root's selected capabilities.
|
|
11
|
+
Unselected capabilities are not fallbacks. Honor higher-priority active-surface
|
|
12
|
+
tool rules. Use the shared development server when needed. Inspect relevant viewports and
|
|
13
|
+
states against the user's requirements and repository design system. Report
|
|
14
|
+
the specific blocker if no available method supports the required judgment.
|
|
15
|
+
|
|
16
|
+
Reuse unaffected evidence. Do not run this loop for logic-only changes.
|
|
17
|
+
Specialists own implementation and delegated interaction checks.
|
|
@@ -1,14 +1,13 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: web-visualize
|
|
3
|
-
description: Use when the user requests an interactive visualization
|
|
3
|
+
description: Use when the user requests or approves an interactive visualization; create a user-facing visual experience from the supplied material.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Use ChatGPT Sites to create an interactive, user-facing visualization that
|
|
7
7
|
turns the supplied plan, analysis, design, structured information, or other
|
|
8
|
-
useful material into a clear, usable result.
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
approval before creating it.
|
|
8
|
+
useful material into a clear, usable result. A visualization request authorizes
|
|
9
|
+
its preparation. Root delegates implementation and judges the rendered result
|
|
10
|
+
with visual-loop; follow the active capability's publication boundary.
|
|
12
11
|
|
|
13
12
|
Return the visualization and enough context to verify that it answers the
|
|
14
13
|
request. If the requested result cannot be completed with an authorized,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
interface:
|
|
2
2
|
display_name: "Web visualize"
|
|
3
3
|
short_description: "Turn useful information into an interactive user-facing visualization."
|
|
4
|
-
default_prompt: "
|
|
4
|
+
default_prompt: "Use $web-visualize for this task."
|
|
5
5
|
policy:
|
|
6
6
|
allow_implicit_invocation: true
|