Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

prompt-template-resolver-parity

Sterne2

Forks1

Aktualisiert15. Mai 2026 um 02:52

Keep prompt template behavior consistent across CLI and cron by reusing one resolver pipeline.

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

sytone

sytone/botnexus

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

Mehr aus diesem Repository

gleiches Repository

gateway-extension-boundary-guard

sytone/botnexus

Prevent gateway projects from taking compile-time dependencies on extension assemblies.

2026-05-142

agent-collaboration

sytone/botnexus

Standard collaboration protocol for all squad agents

2026-05-112

conversation-history-tail-pagination

sytone/botnexus

Prevent refresh regressions by paging conversation history from newest entries

2026-05-082

session-debug

sytone/botnexus

Fast session investigation using BotNexus Probe CLI (preferred) or Python helper scripts. Use when debugging session state, resuming issues, message routing, checking what sessions exist for an agent, reviewing gateway logs for errors, or correlating events across logs/sessions/traces.

2026-05-082

botnexus-issue-workflow

sytone/botnexus

Use when creating GitHub issues, opening worktrees, naming branches, or managing the full lifecycle of a work item on sytone/botnexus. Enforces consistent issue titles, label application, worktree creation, branch naming, PR linking, and cleanup. Triggers on: "create an issue", "open a worktree", "start work on", "file a bug", "add an issue for", "new feature issue", "track this as an issue".

2026-04-282

planning-management

sytone/botnexus

Design spec lifecycle management — creating, reviewing, transitioning, and archiving specs in docs/planning/

2026-04-222

name	prompt-template-resolver-parity
description	Keep prompt template behavior consistent across CLI and cron by reusing one resolver pipeline.
domain	platform-cli
confidence	high
source	earned

Context

Use this when adding or changing prompt-template behavior in CLI, cron, or chat-triggered flows.

Patterns

Reuse CronOptionsPromptTemplateResolver from CLI instead of implementing custom placeholder parsing.
Convert PlatformConfig.PromptTemplates into CronOptions.PromptTemplates before rendering/listing.
Resolve prompt files from BOTNEXUS_HOME so shared (prompts/) and agent/workspace prompt folders are discovered consistently.
Support both .prompt.md and .prompt.json; when both formats exist for the same template name, prefer .prompt.md.
Parse .prompt.md front matter with bounded keys (name, defaults, parameters) and preserve markdown body line breaks for rendering.
Keep prompt run as render-first then gateway /api/chat invocation.

Examples

src\gateway\BotNexus.Cli\Commands\PromptCommands.cs
src\gateway\BotNexus.Cron\Prompts\CronOptionsPromptTemplateResolver.cs

Anti-Patterns

Duplicating regex placeholder parsing in CLI when resolver logic already exists.
Listing only config templates while ignoring file-backed prompt libraries.
Diverging required/default parameter handling between cron and CLI code paths.