菜单
FAST code generation via mcp__cerebras-mcp__write tool using Z.ai glm-4.6. Use for rapid test generation, boilerplate creation, and bulk code tasks in main chat. Prompt must be SHORTER than output. Ideal for tests, CRUD, migrations, and repetitive patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cfn-cerebras-mcp |
| description | FAST code generation via mcp__cerebras-mcp__write tool using Z.ai glm-4.6. Use for rapid test generation, boilerplate creation, and bulk code tasks in main chat. Prompt must be SHORTER than output. Ideal for tests, CRUD, migrations, and repetitive patterns. |
| version | 2.0.0 |
| tags | ["mcp","code-generation","fast","zai","glm-4.6","tests","main-chat"] |
FAST code generation via mcp__cerebras-mcp__write tool using Z.ai glm-4.6 model.
Use for rapid test and code generation when speed matters more than nuance:
Rule: Prompt must be SHORTER than expected output (blueprint style).
mcp__cerebras-mcp__write:
file_path: /absolute/path/to/file.ts
prompt: |
Function: validateEmail(email: string): boolean
Steps:
- Regex test /^[^@]+@[^@]+\.[^@]+$/
- Return boolean result
Imports: none
Errors: none
context_files:
- /path/to/related/file.ts
File: /path/to/file.ts
Function: functionName(params): returnType
Steps:
- Step 1
- Step 2
Imports: import { X } from './y'
Errors: throw new Error("message")
Bad (verbose):
I need you to create a function that validates email addresses.
The function should take an email string as input and return true
if valid or false if invalid...
Good (blueprint):
Function: validateEmail(email: string): boolean
- Regex: /^[^@]+@[^@]+\.[^@]+$/
- Return: true if match, false otherwise
## Known Issues
- ℹ️ **Documentation Only**: This skill describes the MCP tool that's available in the main chat interface
- ℹ️ **No Separate Implementation**: There is no separate script to invoke - the tool is used directly
- ℹ️ **Main Chat Only**: This MCP tool is only available in the main chat, not within spawned agents
Tiered planning orchestrator. Runs the full SPARC+ pipeline (research, spec, decide, pseudo, data, arch, ux, design, test, ops) as a parallel DAG, scaled by build stage (mvp/beta/enterprise) via inclusion profiles. Enforces two gates: every success criterion is executable (verifiable-done) and every step is unambiguous (haiku-executable). Use as the entry point for any non-trivial build instead of cfn-spa-plan.
Post-planning completeness review. Extracts assumptions, traces dependencies, analyzes blast radius, checks alpha-readiness, surfaces gaps before implementation. Use after writing any plan that touches data, APIs, or shared state.
SPARC Specification phase. Make testable acceptance criteria, edge cases, pre/post conditions, invariants BEFORE planning implementation. Use when starting any non-trivial task to lock intent, surface ambiguity early.
Test-strategy phase of cfn-megaplan. Designs test depth properly: fixtures/test-data, the unit/integration/contract/e2e/load split, mocking strategy, and non-functional tests, instead of lumping everything into a vague red phase. Feeds Bar A (verifiable-done): every acceptance criterion becomes a concrete runnable check. Use after cfn-spec, cfn-arch, and (if frontend) cfn-ux.
Pre-edit backup + post-edit validation for safe file edits. Use to capture file state before edits, validate changes after edits, revert files to prior state, or ensure edit safety via auto backup/validation hooks.
Extract complete Redis coordination data from completed CFN Loop tasks and structure into comprehensive JSON analysis files