create-yss-spec 3.0.1 → 3.1.3

package/template/.claude/skills/yss-page-module-development/examples/StandardListPage/hooks/useRuleActions.ts

@@ -1,141 +0,0 @@
-import { message, Modal } from 'ant-design-vue';
-import { useRouter } from 'vue-router';
-import { getPomApi } from '@/api/generated/quality';
-import { RULE_TYPE } from '@/constant'; // 假设项目根目录有全局常量
-import type { QualityRuleItem, TreeNodeData } from '../constant';
-
-/**
- * 质量规则操作逻辑 Hook
- * 处理编辑、删除、运行、状态切换等操作
- */
-export const useRuleActions = (refreshList: () => void) => {
-  const router = useRouter();
-
-  /**
-   * 处理编辑规则
-   * @param row 规则数据行
-   */
-  const handleEdit = (row: QualityRuleItem) => {
-    router.push({
-      path: '/biz/rules/create',
-      query: {
-        id: row.id,
-        formMode: 1,
-        qualityType: RULE_TYPE.BUSINESS,
-      },
-    });
-  };
-
-  /**
-   * 处理删除规则
-   * @param row 规则数据行
-   */
-  const handleDelete = async (row: QualityRuleItem) => {
-    try {
-      const { deleteQualityRule } = getPomApi();
-      await deleteQualityRule({ ids: [row.id] } as any);
-      message.success('删除成功');
-      refreshList();
-    } catch (error) {
-      console.error('删除失败:', error);
-    }
-  };
-
-  /**
-   * 处理运行规则
-   * @param row 规则数据行
-   */
-  const handleRun = async (row: QualityRuleItem) => {
-    try {
-      const { executeQualityCheck } = getPomApi();
-      await executeQualityCheck({
-        ruleCode: row.ruleCode || row.id,
-        qualityType: 'BUSINESS',
-      });
-
-      message.success('运行成功');
-    } catch (error) {
-      console.error('运行失败:', error);
-    }
-  };
-
-  /**
-   * 处理状态切换
-   * @param row 规则数据行
-   */
-  const handleStatusChange = async (row: QualityRuleItem) => {
-    const text = row.status === 1 ? '禁用' : '启用';
-    Modal.confirm({
-      title: `确认${text}`,
-      content: `确认${text}此规则吗？`,
-      okText: '确认',
-      cancelText: '取消',
-      onOk: async () => {
-        try {
-          const newStatus = row.status === 1 ? 0 : 1;
-          const { qualityRuleEnabled } = getPomApi();
-          await qualityRuleEnabled({
-            id: Number(row.id),
-            status: newStatus,
-          });
-          message.success(`${text}成功`);
-          refreshList();
-        } catch (error) {
-          console.error(`${text}失败:`, error);
-        }
-      },
-    });
-  };
-
-  /**
-   * 处理新建规则
-   * @param selectedNode 当前选中的树节点
-   */
-  const handleCreate = (selectedNode: TreeNodeData | null) => {
-    const query: any = {
-      qualityType: 'BUSINESS',
-    };
-
-    if (selectedNode) {
-      if (selectedNode.treeType === '1') {
-        // 规则分类树节点
-        query.dirCode = selectedNode.dirCode;
-      } else if (selectedNode.treeType === '2') {
-        // 数据源树节点
-        query.datasourceName = selectedNode.datasourceName;
-        query.databaseName = selectedNode.databaseName;
-        query.dataBaseType = selectedNode.dataBaseType;
-      }
-    }
-
-    router.push({
-      path: '/biz/rules/create',
-      query,
-    });
-  };
-
-  /**
-   * 处理规则名称点击（跳转详情页）
-   * @param row 规则数据行
-   */
-  const handleRuleNameClick = (row: QualityRuleItem) => {
-    router.push({
-      path: '/rules/detail',
-      query: {
-        id: row.id,
-        templateId: row.templateId,
-        qualityType: RULE_TYPE.BUSINESS,
-        ruleCode: row.ruleCode,
-      },
-    });
-  };
-
-  return {
-    handleEdit,
-    handleDelete,
-    handleRun,
-    handleStatusChange,
-    handleCreate,
-    handleRuleNameClick,
-  };
-};

package/template/.claude/skills/yss-page-module-development/examples/StandardListPage/index.vue

@@ -1,175 +0,0 @@
-<script setup lang="ts">
-import { computed, ref } from 'vue';
-import { Input as AInput, Button as AButton, Switch as ASwitch } from 'ant-design-vue';
-import { RedoOutlined, PlusOutlined } from '@ant-design/icons-vue';
-import { YSplitPane, YCard, YTable } from '@yss-ui/components';
-import { useTableHeight } from '@yss-ui/hooks';
-import { TABLE_COLUMNS, type QualityRuleItem } from './constant';
-import { useQualityRuleList } from './hooks/useQualityRuleList';
-import { useRuleActions } from './hooks/useRuleActions';
-import QualityTree from '@/components/QualityTree/index.vue'; // 假设的树组件
-
-defineOptions({
-  name: 'StandardListPage',
-});
-
-/** 列表数据逻辑 */
-const {
-  tableData,
-  loading,
-  pagination,
-  searchForm,
-  selectedNode,
-  fetchList,
-  handlePageChange,
-  handleSizeChange,
-  handleSearch,
-  handleRefresh,
-  handleTreeNodeClick,
-} = useQualityRuleList();
-
-const tableRef = ref();
-// 自动计算表格高度，使其占满剩余空间
-const { tableHeight } = useTableHeight(tableRef, { withPagination: true });
-
-/** 规则操作逻辑 */
-const { handleEdit, handleDelete, handleRun, handleStatusChange, handleCreate, handleRuleNameClick } =
-  useRuleActions(fetchList);
-
-/**
- * 操作列配置
- * 使用 computed 确保响应式，支持动态显示/隐藏按钮
- */
-const actionConfig = computed(() => ({
-  title: '操作',
-  width: 160,
-  align: 'center' as const,
-  fixed: 'right' as const,
-  buttons: [
-    {
-      text: '编辑',
-      key: 'edit',
-      type: 'link' as const,
-      clickFn: ({ row }: { row: QualityRuleItem }) => handleEdit(row),
-      disabledFn: ({ row }: { row: QualityRuleItem }) => !!row.status,
-    },
-    {
-      text: '运行',
-      key: 'run',
-      type: 'link' as const,
-      isConfirm: true,
-      confirmProps: {
-        title: '确认运行此规则吗？',
-        needLoading: true,
-      },
-      clickFn: async ({ row }: { row: QualityRuleItem }, _btn: any, helpers: any) => {
-        await handleRun(row);
-        helpers?.hideLoading();
-        helpers?.close();
-      },
-    },
-    {
-      text: '删除',
-      key: 'delete',
-      type: 'link' as const,
-      danger: true,
-      isConfirm: true,
-      confirmProps: {
-        title: '确认删除此规则吗？删除后无法恢复',
-        needLoading: true,
-      },
-      clickFn: async ({ row }: { row: QualityRuleItem }, _btn: any, helpers: any) => {
-        await handleDelete(row);
-        helpers?.hideLoading();
-        helpers?.close();
-      },
-      disabledFn: ({ row }: { row: QualityRuleItem }) => !!row.status,
-    },
-  ],
-}));
-
-/**
- * 处理搜索框回车
- */
-const handleSearchPressEnter = () => {
-  handleSearch();
-};
-</script>
-
-<template>
-  <div class="business-quality-rule">
-    <YSplitPane
-      :initial-width="280"
-      :min-width="280"
-      :max-width="480"
-      collapsible
-      storage-key="business-quality-rule-split"
-    >
-      <!-- 左侧：树组件 -->
-      <template #left>
-        <div class="tree-panel">
-          <QualityTree @node-select="handleTreeNodeClick" />
-        </div>
-      </template>
-
-      <!-- 右侧：主内容区 -->
-      <template #right>
-        <y-card class-name="content-panel">
-          <!-- 搜索和操作区 -->
-          <div class="search-bar">
-            <div class="search-inputs">
-              <AInput
-                v-model:value="searchForm.ruleName"
-                placeholder="请输入规则名称"
-                allow-clear
-                style="width: 300px"
-                @press-enter="handleSearchPressEnter"
-              />
-            </div>
-
-            <div class="action-buttons">
-              <AButton :loading="loading" @click="handleRefresh">
-                <template #icon><RedoOutlined /></template>
-                刷新
-              </AButton>
-              <AButton type="primary" @click="() => handleCreate(selectedNode)">
-                <template #icon><PlusOutlined /></template>
-                添加质量规则
-              </AButton>
-            </div>
-          </div>
-
-          <!-- 表格 -->
-          <div ref="tableRef" class="table-container">
-            <YTable
-              :data="tableData"
-              :columns="TABLE_COLUMNS"
-              :loading="loading"
-              :action-config="actionConfig"
-              pageable
-              :max-height="tableHeight"
-              :pagination="pagination"
-              @page-change="handlePageChange"
-              @size-change="handleSizeChange"
-            >
-              <!-- 规则名称列（自定义渲染为链接） -->
-              <template #ruleName="{ row }">
-                <a class="rule-name-link" @click="() => handleRuleNameClick(row)">
-                  {{ row.ruleName }}
-                </a>
-              </template>
-
-              <!-- 状态列（自定义渲染为开关） -->
-              <template #status="{ row }">
-                <ASwitch :checked="row.status === 1" @change="() => handleStatusChange(row)" />
-              </template>
-            </YTable>
-          </div>
-        </y-card>
-      </template>
-    </YSplitPane>
-  </div>
-</template>
-<style lang="less" scoped>
-@import './style.less';
-</style>

package/template/.claude/skills/yss-page-module-development/examples/StandardListPage/style.less

@@ -1,83 +0,0 @@
-@import "@/styles/variables.less";
-
-.business-quality-rule {
-  width: 100%;
-  height: 100%;
-  box-sizing: border-box;
-  display: flex;
-  flex-direction: column;
-
-  /** 树面板样式 */
-  .tree-panel {
-    height: 100%;
-    background-color: #fff;
-    overflow: hidden;
-    display: flex;
-    flex-direction: column;
-    border-radius: 8px;
-  }
-
-  /** 内容面板样式 */
-  .content-panel {
-    height: 100%;
-    display: flex;
-    flex-direction: column;
-    overflow: hidden;
-
-    // CRITICAL: YSplitPane 内部不要加 padding-left，改为给 YCard 加 margin
-    .y-card {
-      margin-left: 12px;
-    }
-
-    // CRITICAL: 让 Card 内容区域支持 flex 布局
-    :deep(.ant-card-body) {
-      height: 100%;
-      display: flex;
-      flex-direction: column;
-      flex: 1;
-      overflow: hidden;
-    }
-
-    // 搜索栏（固定高度）
-    .search-bar {
-      display: flex;
-      justify-content: space-between;
-      align-items: center;
-      padding: 16px;
-      gap: 16px;
-      flex-shrink: 0;
-
-      .search-inputs {
-        display: flex;
-        gap: 8px;
-        align-items: center;
-      }
-
-      .action-buttons {
-        display: flex;
-        gap: 8px;
-      }
-    }
-
-    // 表格容器（使用 flex: 1 占据剩余空间）
-    .table-container {
-      flex: 1; // ← CRITICAL: 让表格区域占据剩余空间
-      overflow: hidden; // ← CRITICAL: 防止溢出
-      display: flex;
-      flex-direction: column;
-      min-height: 0; // 关键：允许 flex 子元素收缩
-    }
-
-    // 规则名称链接样式
-    .rule-name-link {
-      color: @primary-color;
-      cursor: pointer;
-      text-decoration: none;
-      transition: color 0.2s;
-
-      &:hover {
-        text-decoration: underline;
-      }
-    }
-  }
-}

package/template/.claude/skills/yss-page-module-development/references/component-map.md

@@ -1,34 +0,0 @@
-# YSS UI 组件来源速查
-
-此文件用于业务页面生成前的组件选型。优先使用 YSS UI 已封装组件；未封装能力再从 `ant-design-vue` 导入。
-
-## 从 `@yss-ui/components` 导入
-
-| 组件 | 适用场景 | 备注 |
-| --- | --- | --- |
-| `YButton` | 操作按钮、权限按钮 | 支持 `permissionCode`、`fallback`、`modifiers`；优先替代 `a-button`。 |
-| `YCard` | 页面容器、区域容器 | 支持 `title`、`extra`、`padding`、Meta 插槽。 |
-| `YTable` | 标准列表、分页、操作列、筛选、字典翻译 | 继承 vxe-table 能力，分页用 AntDV Pagination。 |
-| `YEditTable` | 可编辑表格 | 需要底部添加按钮高度时配合 `yss-use-table-height`。 |
-| `YTree` | 左侧分类树、组织树、搜索过滤树 | 节点操作用 `getNodeActions`。 |
-| `YSplitPane` | 左树右表、可拖拽分割布局 | 左右或上下区域分割。 |
-| `YFormily` | JSON Schema 表单、新增/编辑/查看 | 默认表单方案。 |
-| `YssFormily` | 表单兼容导出 | 仅用于维护历史代码；新代码统一使用 `YFormily`。 |
-| `YConditionBuilder` | 条件构建器、规则配置 | 常用于数据质量、筛选条件配置。 |
-| `YFileImport` | 文件导入 | Formily schema 内也可用 `YFileImport`。 |
-| `YMonaco` | 代码编辑器 | SQL、JSON、脚本编辑。 |
-| `YMonacoDiff` | 代码 Diff | 变更对比场景。 |
-| `YCron` | Cron 表达式编辑 | 定时任务配置。 |
-| `YMonthCalendar` | 月度日历、节假日和连续区间 | 支持单元格、右键菜单和头部插槽。 |
-| `YEcharts` | 图表展示 | 业务图表封装。 |
-| `YSheet` | 协同/类 Excel 表格 | 复杂表格编辑。 |
-| `AuthorityDropdown` | 权限相关下拉 | 可从 `@yss-ui/components` 导入。 |
-
-## 回退到 `ant-design-vue`
-
-未由 `@yss-ui/components` 导出的组件直接从 `ant-design-vue` 导入，不臆造 Y 前缀。
-
-## 禁止规则
-
-- 不要编造未导出的 Y 前缀组件。
-- 业务层不要从 `@formily/antdv` 导入 UI 适配组件。

package/template/.claude/skills/yss-page-module-development/references/frontend-docs.md

@@ -1,11 +0,0 @@
-# yss-page-module-development Frontend Documentation
-
-Generated: 2026-08-17T12:03:37.436Z
-
-Use these YSS UI documentation entry points as authoritative references when local repo examples are insufficient.
-
-- components: http://192.168.164.27:3200/components
-- hooks: http://192.168.164.27:3200/hooks
-- skills: http://192.168.164.27:3200/skills
-
-When documentation and local code differ, inspect the current project code before editing and prefer established local usage.

package/template/.claude/skills/yss-page-module-development/references/hooks-map.md

@@ -1,11 +0,0 @@
-# YSS UI Hooks 速查
-
-业务页面生成时优先从 `@yss-ui/hooks` 复用 hooks。
-
-## 高度与异步
-
-- `useTableHeight` 和 `useTreeHeight` 必须绑定真实容器 `ref`，并按页面的分页、工具栏、搜索区选择扣除项。
-- `useLoading` 负责异步 loading 和错误边界；Orval mutator 已提示的错误不得在 `onError` 重复提示。
-- `usePollingTask` 只负责轮询调度，不接管页面的 `loading/data/error`。
-- `useUrlState` 用于把查询条件、分页和 Tab 状态同步到 URL。
-- `useFullscreen` 用于容器、图表或编辑器全屏。

package/template/.claude/skills/yss-page-module-development/references/utils-map.md

@@ -1,14 +0,0 @@
-# YSS UI Utils 速查
-
-业务页面生成时优先从 `@yss-ui/utils` 复用工具函数，避免重复实现。
-
-## 常用工具
-
-- 权限：`getAuthBtns`、`hasAuth`、`getBtnInfo`、`clearAuthInfo`。
-- 复制：`copyToClipboard(text)`。
-- 下载：`downloadFileStream`、`getFileNameFromContentDisposition`、`handleBlobResponse`、`downloadFileFromUrl`。
-- 格式化：`formatMoney`、`formatDate`、`formatFileSize`、`formatDateRelative`。
-- 主题：`applyYssTheme`、`lightenColor`、`darkenColor`。
-- URL：`getUrlData`。
-
-接口导出下载必须读取 `file-export-download` 专项技能，优先复用统一的 Blob 响应处理，不在页面 Hook 重复解析文件名和创建下载链接。

package/template/.codex/skills/ask-matt/PHASE-BOUNDARIES.md

@@ -1,55 +0,0 @@
-# Phase boundaries
-
-A **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. The definition is fuzzy on purpose: a phase ends when you think *"ok, we're done with that"*.
-
-The **phase boundary** is the gap between two phases, and it is the only place this decision belongs. Mid-phase there is no decision to make — continue, or split the work that's left into subagents. Compacting mid-phase makes the agent lose the thread.
-
-## The five options
-
-| Option       | What it does                                                    |
-| ------------ | --------------------------------------------------------------- |
-| **Continue** | Stay in the session. No context switch at all.                    |
-| **`/clear`** | Empty the context window and start from nothing.                  |
-| **`/handoff`** | Write a portable markdown file and seed a session anywhere with it. |
-| **Subagent** | Send the task to its own context window and get a report back.     |
-| **`/compact`** | Compress this context and seed a fresh session with the summary.  |
-
-## The tree
-
-Work top to bottom at the boundary. The first **yes** wins.
-
-**1. Can you continue in this session?** Two things make the answer yes: the next phase needs this phase as a **primary source**, or you have enough [smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone) left (~150k tokens) for the next phase to fit. Grilling → implementation is the standard yes: the implementation wants the reasoning verbatim, not a summary of it. Continue costs nothing and loses nothing, so rule it out before anything else.
-
-**2. Is the context irrelevant to what comes next?** Is everything in this session — the exploration, the decisions, the dead ends — disposable? If so, **`/clear`**. It is the cheapest move on the board: it takes no time and hands back the whole window. `/clear` also isn't terminal — the old session stays resumable.
-
-The cost of getting this wrong is one-way. Clear a *relevant* context and you lose the **why** behind what you built, and no amount of reading the diff back gets it returned.
-
-**3. Do you need to hand off?** `/handoff` is narrow. You need it only when you are:
-
-- swapping to a **new harness** (Claude → Codex),
-- moving to a **new directory** or repo,
-- sending the work to a **colleague**,
-- or forking a side task you found **mid-phase** without derailing what you're doing.
-
-That list is the whole clause. What `/handoff` buys is **portability** — a file that travels. If nothing is travelling, you don't need it.
-
-**4. Can the task be done AFK?** Is it scoped tightly enough to run with you away from the keyboard, no steering? Then send it to a **subagent** and leave this session untouched. Automated review is the standard case: the agent reads the diff and reports, and you aren't needed while it does.
-
-**5. Otherwise, `/compact`.** Relevant context, same harness, same directory, and you need to stay in the loop — this is where the tree lands, and it lands here often. Pass it an instruction (`/compact we're going to QA this area`) so the summary keeps what the next phase needs.
-
-`/compact` is the **default, not the first reach**. It sits at the bottom because the four questions above it are all cheaper or more precise. The failure mode when people start here is a fresh session that is confidently wrong about a decision the summary flattened.
-
-## Primary and secondary sources
-
-Every move except **Continue** turns a **primary source** into a **secondary source** — the session as it happened, replaced by a summary of it. The trade is always the same shape:
-
-| Source                            | Information | Noise | Room to move |
-| --------------------------------- | ----------- | ----- | ------------ |
-| Primary (Continue)                | Full        | Lots  | Little       |
-| Secondary (`/compact`, `/handoff`) | Lossy       | Less  | Lots         |
-
-This is why question 1 comes first. You only pay the lossiness when staying costs more than it saves.
-
-## These are judgement calls
-
-The questions are not objective — each has taste in it, and the same boundary can go two ways on two days. The value is in asking them **in order**, at the boundary rather than in the middle of the work.

package/template/.codex/skills/ask-matt/SKILL.md

@@ -1,95 +0,0 @@
----
-name: ask-matt
-description: Ask which skill or flow fits your situation. A router over the skills in this repo.
-disable-model-invocation: true
----
-
-# Ask Matt
-
-You don't remember every skill, so ask.
-
-## YSS default (read this first)
-
-In this template, **`yss-product-lifecycle` is the default orchestrator**. Native work-units own Spec, tickets, implementation authorization, and gates.
-
-This skill is a **Matt compatibility map**. Use `/grill-with-docs`, `/to-spec`, `/to-tickets`, and `/implement` only when the user **explicitly** names them. Do not treat the idea→ship list below as the YSS default. `/implement` does not grant git commit/push. Spec drafts from `/to-spec` stay `ready-for-human` until a human approves the Spec baseline.
-
-A **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.
-
-## Matt compatibility flow: idea → ship
-
-The route most work travels. You have an idea and want it built.
-
-1. **`/grill-with-docs`** — sharpen the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No working directory? Use `/grill-me` — see Standalone. Both run the same `/grilling` primitive; `grill-with-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)
-2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`/handoff`** in both directions (a prototype lives in its own directory, which is exactly what `/handoff` is for — see Phase boundaries):
-   - **`/handoff`** out, then open a fresh session against that file,
-   - **`/prototype`** to answer the question with throwaway code,
-   - **`/handoff`** back what you learned, and reference it from the original idea thread.
-3. **Branch — is this a multi-session build?**
-   - **Yes** → **`/to-spec`** (turn the thread into a spec), then **`/to-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `docs/.scratch/<feature>/issues/`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`/implement`** per ticket, **`/clear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.
-   - **No** → **`/implement`** right here, in the same context window.
-
-   Either way, **`/implement`** builds each issue by driving **`/tdd`** internally — one red-green slice at a time — then closes out by running **`/code-review`** (Standards + Spec, plus UI fidelity when UI is in scope). Do not commit or push from `/implement`. Reach for **`/tdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`/code-review`** on its own whenever you want to review a branch or PR against a fixed point.
-
-### Context hygiene
-
-Keep steps 1–3 in **one unbroken context window** — don't compact or clear until after `/to-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `/implement` then starts fresh, working from the ticket.
-
-The limit on this is the **[smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `/to-tickets`, don't push on degraded — `/compact` at the nearest phase boundary and carry on (see Phase boundaries).
-
-## On-ramps
-
-A starting situation that generates work, then merges onto the main flow.
-
-- **Bugs and requests piling up** → **`/triage`**. It moves issues through triage roles and produces agent-ready issues, which **`/implement`** later picks up.
-
-  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `/to-tickets` produced are already agent-ready, so **don't triage them**.
-
-- **Something's broken** → **`/diagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`/improve-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.
-
-- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`/wayfinder`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Where **`/grill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't — and it's slower and denser, so save it for exactly that, never a well-scoped feature.
-
-  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`/to-spec`**, which collapses the map's linked decisions into a buildable plan, then `/to-tickets` and `/implement` as usual. Looping the map straight into `/implement` skips that collapse and throws the linked detail away — go straight to `/implement` only when the effort turned out genuinely small.
-
-## Codebase health
-
-Not feature work — upkeep.
-
-- **`/improve-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `/grill-with-docs`. It's the survey that finds the candidates; **`/codebase-design`** (below) is the bench you design the chosen one on.
-
-## Vocabulary underneath
-
-Two model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.
-
-- **`/domain-modeling`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word ("account" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `/grill-with-docs` drives to keep `CONTEXT.md` a clean glossary.
-- **`/codebase-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `/tdd` and `/improve-codebase-architecture` both speak it.
-
-## Phase boundaries
-
-A **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:
-
-- **Continue** — stay put. Costs nothing, loses nothing.
-- **`/clear`** — empty the window, when nothing here matters to what's next.
-- **`/handoff`** — write a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.
-- **Subagent** — send a tightly-scoped task to its own window and get a report back.
-- **`/compact`** — compress this context and seed a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.
-
-Read [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree — the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.
-
-## Standalone
-
-Off the main flow entirely.
-
-- **`/grill-me`** — the same relentless interview as `/grill-with-docs`, but **stateless**: it saves nothing locally and builds no `CONTEXT.md`. Reach for it when you are **not working in a working directory** — sharpening a plan, a design, a piece of writing, anything with no repo under it. If you are in a working directory, use `/grill-with-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.
-- **`/grilling`** — the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `/grill-me` and `/grill-with-docs` are the two named ways in, and `/triage`, `/wayfinder` and `/improve-codebase-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.
-- **`/resolving-merge-conflicts`** — work an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finish the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.
-- **`/prototype`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype/<name>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.
-- **`/yss-research`** — investigate technical or strategy evidence using `technical-evidence` / `strategy-evidence` and `quick` / `evidence-audited` modes. Use a background agent when the runtime supports it and parallel reading is useful; delegation is not a trust guarantee. The old `/research` name is a deprecated alias. Research feeds `/grill-with-docs` and lifecycle decisions; it does not approve them.
-- **`/to-questionnaire`** — when the thing blocking you isn't in your head or the codebase but in **someone else's**, this writes them a questionnaire to fill in. It's the inverse of `/grill-me`: instead of interviewing you about the subject, it interviews you about the **send** — who it's going to, what you need back — and aims the questions at the gap. What comes back is material for `/grill-with-docs` or `/to-spec`.
-- **`/wait-what`** — the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `CONTEXT.md` vocabulary. It works after the fact; `/grill-with-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.
-- **`/teach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.
-- **`/writing-for-agents`** — reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.
-
-## Precondition
-
-**`/setup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.

package/template/.codex/skills/ask-matt/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Ask Matt"
-  short_description: "Find the right skill or workflow"
-policy:
-  allow_implicit_invocation: false