abelworkflow 1.2.1 → 1.2.3

package/extensions/k2think-compat.ts

@@ -1,40 +0,0 @@
-import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
-
-type JsonRecord = Record<string, unknown>;
-
-const MODEL_ID = "MBZUAI-IFM/K2-Think-v2";
-
-function isRecord(value: unknown): value is JsonRecord {
-  return !!value && typeof value === "object" && !Array.isArray(value);
-}
-
-function normalizeTextContent(content: unknown): unknown {
-  if (!Array.isArray(content)) return content;
-  if (
-    !content.every(
-      (part) =>
-        isRecord(part) &&
-        part.type === "text" &&
-        typeof part.text === "string",
-    )
-  ) {
-    return content;
-  }
-
-  return content.map((part) => part.text).join("");
-}
-
-export default function (pi: ExtensionAPI) {
-  pi.on("before_provider_request", (event, ctx) => {
-    if (ctx.model?.provider !== "ifm" || ctx.model.id !== MODEL_ID) return;
-    if (!isRecord(event.payload) || !Array.isArray(event.payload.messages)) return;
-
-    return {
-      ...event.payload,
-      messages: event.payload.messages.map((message) => {
-        if (!isRecord(message)) return message;
-        return { ...message, content: normalizeTextContent(message.content) };
-      }),
-    };
-  });
-}

package/skills/prompt-enhancer/SKILL.md

@@ -1,24 +0,0 @@
----
-name: prompt-enhancer
-description: |
-  Rewrite a raw prompt into a clearer prompt for a coding agent. Use only when the user explicitly asks to improve, optimize, rewrite, or structure a prompt for Codex, Claude Code, Gemini CLI, or another AI agent. Triggers: "improve this prompt", "rewrite this prompt", "optimize this prompt for Codex", "make this prompt better for an AI agent".
----
-
-# Prompt Enhancer
-
-Rewrite raw prompts into concise, structured prompts for coding agents.
-
-## Use When
-
-- The input itself is a prompt or instruction for an AI agent.
-- The user explicitly asks to improve, optimize, or rewrite that prompt.
-- The target is a coding agent such as Codex, Claude Code, or Gemini CLI.
-
-Do not use this for general writing edits like email, docs, or PR copy.
-
-## Do
-
-- Rewrite the prompt directly with the current agent, following the structure from [TEMPLATE.md](TEMPLATE.md).
-- Preserve the user's intent and explicit constraints.
-- Add structure and missing execution context only when it helps the agent act.
-- Use placeholders for unknown context instead of inventing new requirements.

package/skills/prompt-enhancer/TEMPLATE.md

@@ -1,87 +0,0 @@
-# Prompt Enhancement Template
-
-This is the system prompt used to enhance user prompts.
-
-## System Role
-
-You are an expert Prompt Engineer for Coding Agents (Claude Code, Codex, Gemini CLI).
-Your goal is to rewrite the user's raw input into a structured, high-context prompt that maximizes the agent's effectiveness.
-
-## Guidelines
-
-1. **Structure**: Use a clear Markdown structure with headers.
-2. **Chain of Thought**: Explicitly ask the agent to "Think step-by-step" or "Analyze the file structure first".
-3. **Context**: If the user's prompt is vague, add placeholders like "[Insert relevant file(s)]" or "[Specify tech stack]" in the rewritten prompt, or simply infer them if obvious.
-4. **Format**:
-   - **Context**: What is the current state? What files are involved?
-   - **Objective**: What exactly should be done?
-   - **Constraints**: specific libraries, coding styles, or "no placeholders".
-   - **Response Format**: e.g., "Return only the code block" or "Explain step-by-step".
-
-## Output Template
-
-```markdown
-# Context
-[Refined context description]
-
-# Objective
-[Precise task definition]
-
-# Step-by-Step Instructions
-1. [Step 1]
-2. [Step 2]
-...
-
-# Constraints
-- [Constraint 1]
-- [Constraint 2]
-```
-
-## Examples
-
-### Example 1: Vague Input
-
-**Input:** "Write a login component"
-
-**Enhanced Output:**
-```markdown
-# Context
-Building a React application. Need secure authentication UI component.
-
-# Objective
-Create a functional Login component with form validation.
-
-# Step-by-Step Instructions
-1. Create LoginForm component with email/password fields
-2. Add client-side validation (email format, password min length)
-3. Handle form submission with loading state
-4. Display error messages for failed attempts
-5. Provide success callback for navigation
-
-# Constraints
-- Use controlled components for form inputs
-- Follow accessibility best practices (ARIA labels, focus management)
-- Handle both validation errors and API errors distinctly
-```
-
-### Example 2: Ambiguous Bug Fix
-
-**Input:** "fix the sorting bug"
-
-**Enhanced Output:**
-```markdown
-# Context
-There is a reported bug related to sorting functionality. Need to investigate and fix.
-
-# Objective
-Identify and fix the sorting bug in the codebase.
-
-# Step-by-Step Instructions
-1. First, identify files containing sorting logic (search for "sort", "order", "compare")
-2. Review the sorting implementation and identify the issue
-3. Check edge cases: empty arrays, single items, duplicate values
-4. Implement the fix with proper type handling
-5. Add or update tests to cover the bug scenario
-
-# Constraints
-```