Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

implementer

Sterne21

Forks1

Aktualisiert21. Mai 2026 um 03:07

Use when acting as the SciStudio implementer persona for scoped code, tests, tool wiring, implementation-linked docs, and gate-record evidence.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

jiazhenz026

jiazhenz026/SciStudio

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	implementer
description	Use when acting as the SciStudio implementer persona for scoped code, tests, tool wiring, implementation-linked docs, and gate-record evidence.

SciStudio Implementer Skill

This skill is a hard pointer only. It does not define independent policy.

Before doing implementer work, load and follow:

@AGENTS.md
@docs/ai-developer/rules.md
@docs/ai-developer/personas/implementer.md
@docs/ai-developer/specific_rules/gated-workflow.md
The matching task-specific rule under @docs/ai-developer/specific_rules/

When dispatched by a manager, also follow @docs/ai-developer/specific_rules/agent-dispatch.md. Do not continue as implementer until the persona file and common rules are loaded.

Mehr aus diesem Repository

gleiches Repository

scistudio

jiazhenz026/SciStudio

Base identity for the SciStudio embedded agent. Lists the 6 task skills available and when to invoke each. Loaded once at session start; task skills load on demand when the user turn matches their trigger description.

2026-07-1521

scistudio-e2e-test

jiazhenz026/SciStudio

Drive a live end-to-end SciStudio session — start the backend (and Vite if needed), open Chrome via Chrome MCP, walk the scenario file the user points at, capture screenshots/console/network as evidence, and write a pass/fail verdict back into that file. Trigger whenever the user says "跑 e2e", "do an e2e", "run e2e on PR

2026-07-0921

scistudio-build-workflow

jiazhenz026/SciStudio

Use when the user wants to design a new workflow, choose block types, wire edges between blocks, or convert a verbal pipeline description into a valid workflow YAML. NOT for debugging existing runs (use scistudio-debug-run) or for writing custom blocks (use scistudio-write-block).

2026-07-0221

scistudio-inspect-data

jiazhenz026/SciStudio

Use when the user wants to look at intermediate or output data — preview a slice of an image, peek at the first rows of a DataFrame, check the shape/dtype of an array, or trace where a data ref came from. NOT for debugging failed runs (use scistudio-debug-run).

2026-07-0221

scistudio-write-block

jiazhenz026/SciStudio

Use when the user wants to author a NEW BLOCK FILE — Python source code (a class subclassing Block / ProcessBlock / IOBlock / AppBlock / CodeBlock with typed ports and a config_schema) that goes in ``<project>/blocks/<name>.py``. ALWAYS check if an existing block satisfies the contract first (call list_blocks first and reuse a match). NOT for ADDING AN EXISTING BLOCK TYPE AS A NODE in a workflow YAML — that's scistudio-build-workflow ("add an imaging.threshold node to my workflow"). NOT for editing an existing block's config (update_block_config). NOT for writing the workflow YAML itself (scistudio-build-workflow).

2026-06-3021

scistudio-debug-run

jiazhenz026/SciStudio

Use when a workflow run has failed, is stuck, or produced unexpected output, and you need to diagnose the cause. Covers run-status inspection, block-log retrieval, lineage navigation, common error signatures, and the finish_ai_block contract for AI block PTYs. NOT for designing new workflows (use scistudio-build-workflow).

2026-06-2921

Jeden Skill mit einem Klick ausführen