speak-swiftly-text-profiles

name	speak-swiftly-text-profiles
description	Use when a user wants to inspect or change SpeakSwiftly text normalization, including built-in style changes, active or stored text profiles, replacement authoring, persistence reload or save operations, and effective-profile verification before speech generation. Use slim MCP resources/prompts for orientation and drafting; use HTTP endpoints for mutations and detailed reads.

SpeakSwiftly Text Profiles

Use this skill for text-normalization work. The local speak_swiftly MCP surface owns broad text-profile inspection and drafting prompts; HTTP owns detailed reads and mutations.

Orientation

• Start with speak-swiftly://text-profiles or GET /text-profiles for any broad question.
• Use GET /text-profiles/style when the user is really asking about the built-in normalization mode.
• Use GET /text-profiles/effective/{profile_id} before speech generation when the user wants to verify what will actually be applied after profile merging.

Mutation Workflow

• Use PUT /text-profiles/style only when the user is intentionally changing the built-in balanced, compact, or explicit mode.
• Use POST /text-profiles/stored for a new stored reusable profile with a simple replacement list.
• Use PUT /text-profiles/stored/{profile_id}/name when the user wants to change the stored display name without recreating the profile.
• Use PUT /text-profiles/active when the user wants one stored profile to become the default active custom profile.
• Use DELETE /text-profiles/stored/{profile_id} only after confirming the exact stored profile_id.
• Use POST /text-profiles/factory-reset when the user wants to clear the stored catalog back to the default profile set.
• Use POST /text-profiles/stored/{profile_id}/reset when the user wants one stored profile cleared back to its default replacement set without deleting it.

Replacement Editing

• Use POST /text-profiles/replacements, PUT /text-profiles/replacements/{replacement_id}, and DELETE /text-profiles/replacements/{replacement_id} for targeted rule edits.
• Use the draft_text_profile and draft_text_replacement prompts when the user is still designing the normalization policy instead of applying a settled edit immediately.
• Prefer whole_token for identifiers and acronyms, and exact_phrase for multi-word substitutions.
• Be deliberate about whether a rule should run before or after built-in normalization.
• Restrict formats when the user only wants the rule to affect source code, CLI output, or another narrow content kind.

Persistence

• Use POST /text-profiles/save when the user wants an explicit persistence checkpoint.
• Use POST /text-profiles/load when another process changed the underlying profile store and the runtime should refresh from disk.
• The best repo-local authoring guidance for these flows lives in the text-profile guide embedded in MCPResources.swift.