@rse/ase 0.0.43 → 0.0.46

package/dst/ase-config.js

@@ -50,7 +50,7 @@ export const projectClassificationPresets = {
     }
 };
 /*  hard-coded map: which scope kinds each variable may be SET on
-    (reads always cascade through the full chain, this restricts writes only);
+    (reads always cascade through the full chain; this restricts writes only);
     keys absent from this map default to all non-"default" scope kinds  */
 export const configWritableScopes = {
     "agent.task": ["session"]

package/dst/ase-hook.js

@@ -177,7 +177,7 @@ export default class HookCommand {
         #{@ase_agent_status} (refreshed on tmux's own interval,
         independent of Claude Code's statusline repaint cadence).
         Notice: the Claude Code statusline is not usable for this case
-        here at all, as it is not repainted during agent processing! */
+        at all, as it is not repainted during agent processing!  */
     writeAgentStatus(status) {
         const icon = status === "busy" ? "▶" : "⏸";
         if (process.env.TMUX !== undefined

package/dst/ase-skills.js

@@ -6,7 +6,7 @@
 import { z } from "zod";
 import { ofetch } from "ofetch";
 import pacote from "pacote";
-/*  reusable functionality: gather per-package metadata in maximum parallel  */
+/*  reusable functionality: gather per-package metadata with maximum parallelism  */
 export class Skills {
     /*  HTTP timeout for the GitHub/npm-downloads side calls  */
     static HTTP_TIMEOUT_MS = 10_000;
@@ -75,7 +75,7 @@ export class Skills {
             return "N.A.";
         }
     }
-    /*  gather metadata for all given components in maximum parallel,
+    /*  gather metadata for all given components with maximum parallelism,
         dispatching on the technology stack:
         -   "JavaScript"/"TypeScript": NPM registry (pacote) + GitHub stars + npm-downloads
         -   "Java"/"Kotlin"/"Unknown": not yet supported -- return empty result  */
@@ -160,7 +160,7 @@ export class SkillsMCP {
     register(mcp) {
         mcp.registerTool("component_info", {
             title: "ASE component info",
-            description: "Gather metadata for a list of NPM packages in maximum parallel. " +
+            description: "Gather metadata for a list of NPM packages with maximum parallelism. " +
                 "For each package, fetches the full registry packument via `pacote` " +
                 "(in-process, no `npm view` subprocess), the GitHub `stargazers_count` " +
                 "from `api.github.com` (if the repository points to GitHub), and the " +

package/dst/ase-statusline.js

@@ -481,7 +481,7 @@ export default class StatuslineCommand {
             /*  send output  */
             process.stdout.write(out);
             /*  optionally publish task id to the calling tmux pane as a per-pane user
-                option, so someone (like claudeX) can pick it up via #{@ase_task_id}  */
+                option, so something (like claudeX) can pick it up via #{@ase_task_id}  */
             if (process.env.TMUX !== undefined
                 && process.env.TMUX !== ""
                 && process.env.TMUX_PANE !== undefined

package/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.43",
+    "version":                              "0.0.46",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.43",
+    "version":     "0.0.46",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/.github/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name":        "ase",
-    "version":     "0.0.43",
+    "version":     "0.0.46",
     "description": "Agentic Software Engineering (ASE)",
     "keywords":    [ "agentic", "software", "engineering" ],
     "homepage":    "https://ase.tools",

package/plugin/meta/ase-constitution.md

@@ -21,7 +21,7 @@ Prohibitions
 - Do *not* factor out (move) code into own functions without good reason, like necessary reusability.
 - Do *not* use braces around single statement blocks in "if" and "while" constructs unless the language requires them.
 - Do *not* insist on early "return" in "if" blocks if an "else" block exists.
-- Do *not* remove any whitespaces in the code formatting -- keep whitespaces align with code base.
+- Do *not* remove any whitespaces in the code formatting -- keep whitespaces aligned with code base.
 - Do *not* show just partial code changes -- always show complete changes.
 - Do *not* produce any line which consists of just one or more space characters before the newline -- use just the newline.
 - Do *not* use semicolons where they are syntactically optional, except inside `for` clauses.
@@ -50,7 +50,7 @@ Commandments
 - Try to *vertically align similar operators* on consecutive, similar lines.
 - Place spaces after opening and before closing angle brackets and braces.
 - Use *double-quotes* (`"[...]"`) instead of single-quotes (`'[...]'`) for all strings.
-- Use K&R coding style with *opening braces* at end of lines and *closing braces* at the begin of lines.
+- Use K&R coding style with *opening braces* at end of lines and *closing braces* at the beginning of lines.
 - When a language has a *more strongly-typed variant*, prefer that
   variant (e.g., TypeScript over JavaScript, Python with type hints
   over untyped Python).

package/plugin/meta/ase-persona.md

@@ -1,36 +1,43 @@
 
-Ruleset Levels
---------------
+Persona Ruleset Levels
+----------------------
+
+### Level 0
+
+<define name="level0">
+-   You *MUST* *always keep* technical terms exactly.
+-   You *MUST* *always keep* errors quoted exactly.
+-   You *MUST* *always keep* code blocks unchanged.
+</define>
 
 ### Level 1
 
 <define name="level1">
--   You *MUST* *use* short synonyms
-    ("big" not "extensive", "fix" not "implement a solution for").
--   You *MUST* *drop* filler
+-   You *MUST* *drop* filler words
     ("just", "really", "basically", "actually", "simply", etc).
 -   You *MUST* *drop* pleasantries
     ("sure", "certainly", "of course", "happy to", etc).
 -   You *MUST* *drop* hedging
     ("I think", "maybe", "perhaps", "it seems", "sort of", "probably", "I'm not sure but...", "it might be", etc).
--   You *MUST* *keep* technical terms exactly.
--   You *MUST* *keep* code blocks unchanged.
--   You *MUST* *keep* errors quoted exactly.
--   You *MUST* *use* diagrams instead of prose when a topic this way can be explained more consisely.
+-   You *MUST* *prefer* lists with bullet points, instead of long prose paragraphs.
+-   You *MUST* *prefer* bullet points with one or two sentences.
 </define>
 
 ### Level 2
 
 <define name="level2">
+-   You *MUST* *use* shorter synonyms
+    ("big" not "extensive", "fix" not "implement a solution for").
 -   You *MUST* *use* abbreviations
     ("DB", "auth", "config", "req", "res", "fn", "impl", etc).
 -   You *MUST* *use* arrows for causality
     ("X → Y").
+-   You *MUST* *use* em-dashes for short subsequent facts
+    ("X — Y").
 -   You *MUST* *drop* articles
     ("a", "an", "the", etc).
--   You *MUST* *drop* conjunctions
-    ("and", "but", "or", "so", "because", "however", "therefore", "although"),
-    and instead *use* short sentences.
+-   You *MUST* *use* short separate sentences instead of conjunctions
+    ("and", "but", "or", "so", "because", "however", "therefore", "although").
 -   You *MUST* *drop* all fluff in wording.
 </define>
 
@@ -40,12 +47,12 @@ Ruleset Levels
 -   You *MUST* *use* only one word, when one word is clear enough.
 -   You *MUST* *use* only two words, when two words are clear enough.
 -   You *MUST* *use* the three sentence patterns
-    (dependending what information has to be expressed):
+    (depending what information has to be expressed):
     -   `<subject/> <action/> <object/>, <reason/>.` → e.g. "Cat eats fish, hungry."
     -   `<subject/> <action/> <object/>.`            → e.g. "Dog chases ball."
     -   `<subject/> <action/>.`                      → e.g. "Birds fly."
--   You *MUST* *drop* all lists and just provide very short sentences.
--   You *MUST* *keep* all technical substance.
+-   You *MUST* *drop* all lists and their bullet points and instead
+    provide very short subsequent sentences only.
 </define>
 
 Apply Persona
@@ -55,23 +62,26 @@ Apply Persona
 rules even if later skill rules say different:
 
 -   <if condition="<ase-persona-style/> is 'writer'">
-    -   You *MUST* use a decorative, eloquent, and explaining communication style of a writer.
-    -   This is your default style of communication where no rulesets are applied.
+    -   You *MUST* use the decorative, eloquent, and explaining communication style of a *writer*.
+    -   Apply ruleset "level0": <expand name="level0"/>
     </if>
 
 -   <if condition="<ase-persona-style/> is 'engineer'">
-    -   You *MUST* use a brief, factual, and accurate communication style of an engineer.
+    -   You *MUST* use the concise, factual, and accurate communication style of an *engineer*.
+    -   Apply ruleset "level0": <expand name="level0"/>
     -   Apply ruleset "level1": <expand name="level1"/>
     </if>
 
 -   <if condition="<ase-persona-style/> is 'telegrapher'">
-    -   You *MUST* use a very brief, factual, and abbreviating communication style of a telegrapher.
+    -   You *MUST* use the brief, factual, and abbreviating communication style of a *telegrapher*.
+    -   Apply ruleset "level0": <expand name="level0"/>
     -   Apply ruleset "level1": <expand name="level1"/>
     -   Apply ruleset "level2": <expand name="level2"/>
     </if>
 
 -   <if condition="<ase-persona-style/> is 'caveman'">
-    -   You *MUST* use an ultra brief, rough and stuttering communication style of a caveman.
+    -   You *MUST* use the terse, rough and stuttering communication style of a *caveman*.
+    -   Apply ruleset "level0": <expand name="level0"/>
     -   Apply ruleset "level1": <expand name="level1"/>
     -   Apply ruleset "level2": <expand name="level2"/>
     -   Apply ruleset "level3": <expand name="level3"/>

package/plugin/meta/ase-plan.md

@@ -51,7 +51,7 @@ You *MUST* honor the following hints on this *task plan* format:
 -   The <timestamp-created/> is the timestamp when this feature
     crafting specification was created. The
     <timestamp-modified/> is the timestamp when this feature
-    specification was last modified. Both use a ISO-style format
+    specification was last modified. Both use an ISO-style format
     value. The value of both can be determined by
     a call to the `timestamp(format: "yyyy-LL-dd HH:mm")`
     tool of the `ase` MCP service and use the `text` field of

package/plugin/package.json

@@ -6,7 +6,7 @@
     "homepage":                             "http://github.com/rse/ase",
     "repository":                           { "url": "git+https://github.com/rse/ase.git", "type": "git" },
     "bugs":                                 { "url": "http://github.com/rse/ase/issues" },
-    "version":                              "0.0.43",
+    "version":                              "0.0.46",
     "license":                              "GPL-3.0-only",
     "author": {
         "name":                             "Dr. Ralf S. Engelschall",

package/plugin/skills/ase-code-craft/SKILL.md

@@ -107,7 +107,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     7.  Ask the user for clarification if the goal of this crafting is too
         unclear.
 
-    8.  Do not output anything in this step, except you asked the user.
+    8.  Do not output anything in this step, unless you asked the user.
 
 2.  **Investigate Code Base**:
 
@@ -127,7 +127,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -162,7 +162,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             to change.
 
         -   **Loose Coupling, High Cohesion**:
-            Strike for good modularity by a set of small, focused parts
+            Strive for good modularity by a set of small, focused parts
             (high cohesion), connected by thin, explicit wires and
             interfaces (loose coupling).
 
@@ -229,7 +229,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-code-explain/SKILL.md

@@ -27,7 +27,7 @@ specialized in *explaining source code*.
 
 <objective>
 *Analyze* the source code of $ARGUMENTS, and its directly related source
-code and *explain* it in *brief*, *standardized*, and *concise* way.
+code and *explain* it in a *brief*, *standardized*, and *concise* way.
 </objective>
 
 <flow>

package/plugin/skills/ase-code-insight/SKILL.md

@@ -64,7 +64,7 @@ Give *insights* into the project through the source code of $ARGUMENTS.
     </step>
 
 3.  <step id="STEP 3: SOURCE CHURN">
-    Display the source files with caused the most churn by
+    Display the source files which caused the most churn by
     figuring out which source files have the most commits.
     Display the following <template/>:
 

package/plugin/skills/ase-code-lint/SKILL.md

@@ -87,7 +87,7 @@ related to a set of code quality aspects.
 2.  <step id="A01 - FORMATTING">
     <expand name="linter" arg1="A01 - FORMATTING">
     Check for inconsistently formatted code and badly vertically
-    aligned code on sub-sequent lines.
+    aligned code on subsequent lines.
 
     For vertical alignment, prefer to align on operators. For
     continuous code blocks (those without any blank lines at all),
@@ -135,7 +135,7 @@ related to a set of code quality aspects.
     Check for extremely long functions, and deeply nested code
     constructs.
 
-    Especially, for functions prefer fewer then 100 lines, and for
+    Especially, for functions prefer fewer than 100 lines, and for
     nested constructs prefer fewer than 10 nesting levels.
     </expand>
     </step>
@@ -187,7 +187,7 @@ related to a set of code quality aspects.
     <expand name="linter" arg1="A08 - COMPLICATENESS">
     Check for complicated or cumbersome code constructs.
 
-    Especially, check for unnecessary difficult code constructs
+    Especially, check for unnecessarily difficult code constructs
     for which simpler solutions exist.
     </expand>
     </step>
@@ -196,9 +196,9 @@ related to a set of code quality aspects.
     <expand name="linter" arg1="A09 - CONCISENESS">
     Check for non-concise and boilerplate-based code.
 
-    Especially, check for unnecessary long code constructs for
+    Especially, check for unnecessarily long code constructs for
     which shorter solutions exist, and check for unnecessary
-    technical/infrastructural code with too less domain-specific
+    technical/infrastructural code with too few domain-specific
     aspects.
     </expand>
     </step>

package/plugin/skills/ase-code-refactor/SKILL.md

@@ -107,7 +107,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     7.  Ask the user for clarification if the goal of this refactoring is
         too unclear.
 
-    8.  Do not output anything in this step, except you asked the user.
+    8.  Do not output anything in this step, unless you asked the user.
 
 2.  **Investigate Code Base**:
 
@@ -127,7 +127,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -155,7 +155,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             to change.
 
         -   **Loose Coupling, High Cohesion**:
-            Strike for good modularity by a set of small, focused parts
+            Strive for good modularity by a set of small, focused parts
             (high cohesion), connected by thin, explicit wires and
             interfaces (loose coupling).
 
@@ -219,7 +219,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-code-resolve/SKILL.md

@@ -119,7 +119,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     8.  Ask the user for clarification if the goal of this resolution is
         too unclear.
 
-    9.  Do not output anything in this step, except you asked the user.
+    9.  Do not output anything in this step, unless you asked the user.
 
     10. Investigate and *figure out details* related to this problem.
         Report those details with the following <template/>:
@@ -155,7 +155,7 @@ permitted way to persist artifacts is via `task_save(...)`.
           `erDiagram`, depending on intent) and invoking the
           `ase-meta-diagram` skill by calling the tool `Skill(skill:
           "ase:ase-meta-diagram", args: <mermaid-spec/>)`. Omit
-          <optional-diagram/> entirely for simple or purely local situation.
+          <optional-diagram/> entirely for simple or purely local situations.
 
 2.  **Investigate Code Base**:
 
@@ -175,7 +175,7 @@ permitted way to persist artifacts is via `task_save(...)`.
     1.  Generic Tenets:
 
         -   **Separation of Concerns**:
-            Clearly separate all individual concerns as good as possible.
+            Clearly separate all individual concerns as well as possible.
 
         -   **Code Base Alignment**:
             Strictly align with the existing source code base by exactly
@@ -189,7 +189,7 @@ permitted way to persist artifacts is via `task_save(...)`.
 
         -   **No Cleanups**:
             Strictly focus on resolving the problem and do not mix this
-            task with any other necessary code cleanups, except they are
+            task with any other necessary code cleanups, unless they are
             really necessary for resolving the task.
 
         -   **Minimum Flags**:
@@ -207,7 +207,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             Problems for *obvious, particular, or expected* errors
             *should* be handled *near the origin*. Problems for
             *theoretical, fictive, or unexpected* errors, *should* be
-            handled more general and in parent scopes.
+            handled more generally and in parent scopes.
 
 4.  **Find Problem Resolution Approaches**:
 
@@ -265,7 +265,7 @@ permitted way to persist artifacts is via `task_save(...)`.
             a *separate* `ase-meta-diagram` invocation and stack the
             rendered blocks *vertically* (labels `**Before:**` /
             `**After:**`); never side-by-side. Omit <optional-diagram/>
-            entirely for simple or purely local situation.
+            entirely for simple or purely local situations.
 
     6.  Indicate end of reporting by showing the following <template/>:
 

package/plugin/skills/ase-docs-proofread/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: ase-docs-proofread
+argument-hint: "<docs-reference>"
+description: >
+    Analyze the documents for spelling, punctuation, or grammar errors.
+    Use when the user wants to "spellcheck", "proofread", or "lint" a text or document.
+user-invocable: true
+disable-model-invocation: false
+effort: high
+---
+
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+
+Proofread Documentation
+=======================
+
+<skill name="ase-docs-proofread">
+Analyze the documents for spelling, punctuation, or grammar errors.
+</skill>
+
+<role>
+Your role is an experienced, *expert-level proofreader*, specialized in
+checking and correcting the *spelling*, *punctuation* and *grammar* of
+documents.
+</role>
+
+<objective>
+*Analyze* the documents of $ARGUMENTS for problems in their *spelling*,
+*punctuation* or *grammar* and immediately correct all found problems.
+</objective>
+
+<flow>
+
+1.  <step id="STEP 1: Investigation & Checking">
+    Investigate on the document base by using the `Read` tool to read all
+    referenced document files. For all contained texts in those files,
+    check the following problem types *ONLY*:
+
+    - **Spelling**
+    - **Punctuation**
+    - **Grammar**
+
+    You *MUST* collect *all* found problems into an internal list only,
+    and then set <problems/> to the value of this list.
+
+    You *MUST* *NOT* propose document changes in this step 1.
+    You *MUST* *NOT* output anything in this step 1.
+    </step>
+
+2.  <step id="STEP 2: Summary">
+    Use the following <template/> to give a summary of the detected
+    problems in <problems/>:
+
+    <template>
+    | *Proofread Type* | *Proofread Result*      |
+    | ---------------- | ----------------------- |
+    | **SPELLING**:    | **<n/>** problems found |
+    | **PUNCTUATION**: | **<m/>** problems found |
+    | **GRAMMAR**:     | **<k/>** problems found |
+    </template>
+
+    Hints:
+
+    -   <n/> is the number of spelling problems in <problems/>
+    -   <m/> is the number of punctuation problems in <problems/>
+    -   <k/> is the number of grammar problems in <problems/>
+    </step>
+
+3.  <step id="STEP 3: Details & Correction">
+
+    <for items="<problems/>">
+
+    For the current <item/> from the collected list <problems/>, do the
+    following:
+
+    1.  Report the problem with the following <template/>:
+
+        <template>
+        &#x1F7E0; **<type/>**: [`<file/>`:<line/>]: <description/>
+        </template>
+
+        Hints:
+
+        -   The <type/> is `SPELLING`, `PUNCTUATION` or `GRAMMAR`
+            of <item/>.
+
+        -   The <file/> is the name of the document artifact of <item/>.
+            The <line/> is the line number of the document artifact of <item/>.
+
+        -   The <description/> is an ultra brief and concise description
+            of the problem <item/> with a hint what is wrong and why
+            it is wrong. In <description/>, markup all verbatim words
+            <words/> related to the checked text (or the proposed
+            corrected text) as quoted strings containing monospaced text
+            with the Markdown <template>"`<words/>`"</template>.
+
+    2.  Propose a direct change to the corresponding document via the
+        interactive `Edit` tool.
+
+        **IMPORTANT**: Regardless of whether the change was *accepted*
+        or *rejected* by the user (i.e., even if the `Edit` tool returns
+        an error like "The user doesn't want to proceed with this tool
+        use" or "User rejected"), you *MUST* immediately *CONTINUE* with
+        the *next* <item/> in the iteration.
+
+        Do *NOT* stop. Do *NOT* ask the user for confirmation. Do *NOT*
+        summarize. A rejection is *NOT* a signal to abort; it is only
+        a signal that *this one* change is skipped. Only after *all*
+        problems have been processed may you stop.
+
+    </for>
+
+    You *MUST* *NOT* output any further additional explanations or
+    summaries at the end of this skill processing.
+    </step>
+
+</flow>
+

package/plugin/skills/ase-meta-changes/SKILL.md

@@ -33,7 +33,7 @@ based on underlying *Git* commit messages.
 </objective>
 
 For this, understand that ChangeLog entries are
-are always formatted `<prefix/>: <summary/>` where
+always formatted `<prefix/>: <summary/>` where
 the <prefix/> is one of the following tags
 and their usual related changes...
 
@@ -78,8 +78,8 @@ are also grouped and sorted according to the above <prefix/>es.
    *consolidate* the entries in the first (most recent) section only,
    by summarizing and merging closely related entries.
    Perform the entry consolidation per prefix group only.
-   If a changelog <summary/> is too short or is too less comprehensible
-   because of too less context, add some context, especially references
+   If a changelog <summary/> is too short or is too little comprehensible
+   because of too little context, add some context, especially references
    to the class/module/package, etc.
    </step>
 

package/plugin/skills/ase-meta-chat/SKILL.md

@@ -3,7 +3,7 @@ name: ase-meta-chat
 argument-hint: "<llm> <query>"
 description: >
     Query foreign LLM for Chat.
-    Use this skill if a foreign LLM like OpenAI ChatCGPT, Google Gemini,
+    Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini,
     DeepSeek or xAI Grok should be queried with a single chat message.
 user-invocable: true
 disable-model-invocation: false

package/plugin/skills/ase-meta-commit/SKILL.md

@@ -24,7 +24,7 @@ Your role is an experienced, *expert-level software developer*,
 specialized in *Git commit messages*.
 
 <objective>
-Help to *craft* a *consise commit message* for the
+Help to *craft* a *concise commit message* for the
 currently staged Git changes.
 </objective>
 

package/plugin/skills/ase-meta-diagram/SKILL.md

@@ -7,7 +7,7 @@ description: >
     control-flow/branching/concurrency as Flowchart,
     state-machine/states/transitions as an UML State Diagram,
     data-flow/actors/messages/protocols as an UML Sequence Diagram,
-    data-structure/classes/methods as an UML Class Diagram
+    data-structure/classes/methods as an UML Class Diagram,
     data-model/entities/relationships as an ER Diagram, or
     metrics/distributions/time-series as XY-Charts.
 user-invocable: false

package/plugin/skills/ase-meta-evaluate/SKILL.md

@@ -116,7 +116,7 @@ multi-*criteria* decision matrix.
     -   From the <request>$ARGUMENTS</request>, try to derive the criteria
         <criteria-L/> (L=1-M) for the evaluation. Do not output anything.
 
-    -   For each criteria <criteria-L/> (L=1-M), decide on its <weight-L/>
+    -   For each criterion <criteria-L/> (L=1-M), decide on its <weight-L/>
         from the value set { 4.00, 2.00, 1.00, 0.50, 0.25 } (from most
         important, over normal, to less important). Do not output anything.
 
@@ -146,9 +146,9 @@ multi-*criteria* decision matrix.
     </step>
 
 4.  <step id="STEP 4: Evaluate Alternatives against Criteria">
-    -   For each alternative <alternative-K/> (K=1-N) and each criteria
+    -   For each alternative <alternative-K/> (K=1-N) and each criterion
         <criteria-L/> (L=1-M), decide on the evaluation <eval-K-L/>, which
-        means how good the alternative meets the criteria on a Likert-scale
+        means how well the alternative meets the criterion on a Likert-scale
         from { -2, -1, 0, +1, +2 } (from worst, over neutral, to best). Do
         not output anything.
 

package/plugin/skills/ase-meta-persona/SKILL.md

@@ -2,53 +2,57 @@
 name: ase-meta-persona
 argument-hint: "[<persona>]"
 description: >
-    Adjust communication style in four intensivity levels of token usage.
-    The <persona> can be either a decorative, eloquent, and explaining "writer",
-    a brief, factual, and accurate "engineer" (default),
-    a very brief, factual, and abbreviating "telegrapher",
-    or an ultra brief, rough and stuttering "caveman".
+    Adjust communication style in four intensity levels of token usage.
+    The <persona> can be either the decorative, eloquent, and explaining "writer",
+    the concise, factual, and accurate "engineer" (default),
+    the brief, factual, and abbreviating "telegrapher",
+    the terse, rough and stuttering "caveman".
     Use when user says "persona <persona>" or "be <persona>".
 user-invocable: true
 disable-model-invocation: false
 ---
 
+@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
+@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
+
 Persona Configuration
 =====================
 
 1.  Determine request:
     <request>$ARGUMENTS</request>
+    Do not output anything.
 
 2.  <if condition="<request/> is empty">
-    -   Call the `persona(session: <ase-session-id/>)`
+    1.  Call the `persona(session: <ase-session-id/>)`
         tool from the `ase` MCP service and set
         <ase-persona-style/> to its `text` output.
+        Do not output anything.
+
+    2.  Output the following <template/>:
 
-    -   Output:
         <template>
         ⧉ **ASE**: ☯ persona: **<ase-persona-style/>**
         </template>
     </if>
 
 3.  <if condition="<request/> is NOT empty">
-    -   If <request/> is NEITHER 'writer', 'engineer', 'telegrapher', NOR 'caveman',
-        report this with the following <template/> and stop immediately:
+    1.  If <request/> is NEITHER 'writer', 'engineer', 'telegrapher',
+        NOR 'caveman', report this with the following <template/> and then
+        *STOP* immediately:
+
         <template>
-        ⧉ **ASE**: **ERROR:** invalid persona: "<request/>" (expected "writer", "engineer", "telegrapher", or "caveman")
+        ⧉ **ASE**: **ERROR:** invalid persona: "<request/>" (expected `writer`, `engineer`, `telegrapher`, or `caveman`)
         </template>
 
-    -   Set <ase-persona-style><request/></ase-persona-style> and
-        call the `persona(style: <ase-persona-style/>, session: <ase-session-id/>)`
-        tool from the `ase` MCP service.
+    2.  Set <ase-persona-style><request/></ase-persona-style> and
+        call the `persona(style: <ase-persona-style/>, session:
+        <ase-session-id/>)` tool from the `ase` MCP service. Do not
+        output anything.
+
+    3.  Output the following <template/>:
 
-    -   Output:
         <template>
         ⧉ **ASE**: ☯ persona: **<ase-persona-style/>** (*updated*)
         </template>
     </if>
 
-Apply Persona
--------------
-
-@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
-@${CLAUDE_SKILL_DIR}/../../meta/ase-persona.md
-

package/plugin/skills/ase-meta-quorum/SKILL.md

@@ -83,7 +83,7 @@ by querying *multiple* AIs for an *optimal consensus*.
 
     If not all AIs agree, determine a <disagreement/> information,
     formatted as `(disagreement: <ai/>, <ai/>, [...])` where <ai/> is a
-    name of an AI which disagreed from the consensus. Else, if all AIs
+    name of an AI which disagreed with the consensus. Else, if all AIs
     agree, set <disagreement></disagreement>.
     </step>
 

package/plugin/skills/ase-meta-why/SKILL.md

@@ -22,7 +22,7 @@ Your role is an *expert-level assistant*.
 
 <objective>
 Apply the *Five-Whys* *root-cause analysis* technique to investigate
-on the following problem:
+the following problem:
 
 <problem>Why $ARGUMENTS?</problem>
 
@@ -48,7 +48,7 @@ addressing surface-level symptoms.
         Ask <question/> and document the answer in <answer/> with the following template:
         Don't stop at symptoms, keep digging for systemic issues.
         Multiple root-causes may exist -- explore different branches.
-        Consider both technical, domain-specific, process-related or organizational causes.
+        Consider technical, domain-specific, process-related, or organizational causes.
 
         <template>
         &#x26AA; **WHY <item/>**: <answer/>

package/plugin/skills/ase-task-edit/SKILL.md

@@ -277,7 +277,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
 
     1.  *Update timestamp*:
         <if condition="<content/> contains '✎ modified:' AND <content-dirty/> is 'true'">
-        Set update <timestamp-modified/> with the current time in
+        Update <timestamp-modified/> with the current time in
         ISO-style format, which has to be determined by calling the
         `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
         MCP service and use the `text` field of its response. Update

package/plugin/skills/ase-task-preflight/SKILL.md

@@ -126,7 +126,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         </template>
 
     3.  <if condition="<content/> contains '✎ modified:'">
-        Set update <timestamp-modified/> with the current time in
+        Update <timestamp-modified/> with the current time in
         ISO-style format, which has to be determined by calling the
         `timestamp(format: "yyyy-LL-dd HH:mm")` tool of the `ase`
         MCP service and use the `text` field of its response. Update

package/plugin/skills/ase-task-view/SKILL.md

@@ -71,7 +71,7 @@ explicitly requested by this procedure via outputs based on a <template/>!
         *Render plan*: Only output the following <template/>, so the user
         can read the plan and react to it. Do *not* truncate, summarize,
         or partially show the plan -- always show the complete plan
-        <content/> here:.
+        <content/> here.
 
         <template>
         ⧉ **ASE**: ┈┈┈┈┈┈┈┈────────━━━━━━━━**(** `TASK-PLAN-BEGIN` **)**━━━━━━━━────────┈┈┈┈┈┈┈┈