跳到正文
cccskills
免费在 GitHub 公开

charted-scaffold

Writes work-in-progress code and tests based on design doc

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Context

  • designDocPath: $ARGUMENTS[0]
  • prNumber: $ARGUMENTS[1]

Task

Based on the following design doc ${designDocPath}, write WIP code for implementation described in the design doc.

  • Focus only on the PR #${prNumber} if provided.
  • If you add a new class, function, or method, make it throw a "🚧 work in progress" error and add the "@deprecated 🚧 work in progress" tag to its jsdoc.
  • If you add a new component, add the "@deprecated 🚧 work in progress" tag to its jsdoc but do not implement the template or methods.
  • DO NOT ADD ANY NEW BEHAVIOR.
    • As an example, do not add child components in a component.
  • DO NOT CHANGE ANY EXISTING BEHAVIOR:
    • If you change a function or a method signature in a retro-compatible way, do not throw a "🚧 work in progress" error.
    • If the function or method receives a new optional parameter, make it throw a "🚧 work in progress" error if the parameter is set.
    • Even if the goal of the PR is to change the behavior of an existing function or method, do not throw a "🚧 work in progress" error. KEEP THE EXISTING BEHAVIOR.
  • For WIP tests, put the test's steps from the design doc as-is in a comment inside the body of the "it.todo" test.

Examples

WIP class example

/**
 * @deprecated 🚧 work in progress
 */
class Greetings {
  hello() {
    throw new Error(`🚧 work in progress`);
  }
}

WIP method example

class Greetings {
  /**
   * @deprecated 🚧 work in progress
   */
  hello() {
    throw new Error(`🚧 work in progress`);
  }
}

WIP component

/**
 * @deprecated 🚧 work in progress
 */
@Component({
  changeDetection: ChangeDetectionStrategy.OnPush,
  selector: "wm-rules",
  template: `Rules - 🚧 work in progress`,
})
class Rules {
  rules = input.required<Rule[]>();
  ruleSelect = output<Rule>();
}

WIP tests example

Note: test names start in lower case (e.g. "search rules ...").

import { describe, it } from "vitest";

describe(RuleSearch.name, () => {
  it.todo("search rules without filtering", () => {
    // mount RuleSearch
    // click on first rule
    // assert output was triggered once
  });

  it.todo("...", () => {
    // ...
  });
});

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Continues Charted Coding work for a PR by routing to scaffold, red, or green based on design doc progress. Use when resuming work on a PR, continuing TDD after a break, or when the user invokes charted continue with a design doc and PR number.

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

Interviews the user section by section to collaboratively produce design documents. Use when creating a design doc, starting feature design, or when the user invokes the design command.

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

Progressively activates todo tests one at a time, updates implementation code until each passes (verified via Wallaby), checks off matching design doc progress, then moves to the next—following the design doc as the single source of truth.

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

Runs Charted Coding iterations in a loop — route via charted-continue, batch red or green work for an entire test file, commit, then repeat until the PR is complete. Infers design doc and PR number when omitted. Use when the user invokes charted loop, wants batch TDD for a PR test file, or asks to continue charted work with commits.

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

Writes the next failing test based on provided design doc and existing todo tests

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

Reviews a design doc with expert sub-agents

中文简介正在准备中。当前显示原文说明。

testmex/testmex42026年7月23日 更新

查看 testmex 的全部技能

报告此技能的问题