skills.rest
citum
citumOFFICIAL
Explore all skills by this author →
WebsiteGitHub

styleauthor

Alias the style-evolve workflow for backward-compatible legacy references.

31|Updated Jan 28, 2026
Search Tags:#legacy alias#workflow compatibility#style-evolve#prompt aliasing#policy guidance#style authoring
One-click install
npx skills add https://github.com/citum/citum-core --skill styleauthor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: styleauthor
Source: https://github.com/citum/citum-core/tree/main/.skills/styleauthor
Command: npx skills add https://github.com/citum/citum-core --skill styleauthor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves compatibility breaks when older documentation or automation pipelines still reference the legacy style author alias instead of the current style-evolve workflow.

Core Features & Use Cases

  • Legacy alias for style-evolve: Keeps existing workflows working without duplicating logic or changing behavior.
  • Shared workflow docs: Uses the same decision and execution guidance as style-evolve to ensure consistency across the platform.
  • Backwards-compatible usage: Helps teams upgrade without immediately rewriting all prompts, scripts, or references.

Quick Start

Use the styleauthor skill to apply the legacy alias for style-evolve and keep older workflows functioning.

Frequently Asked Questions about styleauthor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep legacy styleauthor workflow aliases running without rewriting scripts?▼

To keep legacy styleauthor workflow aliases running, you use a backward-compatible alias that maps to the style-evolve workflow. This ensures existing scripts and documentation function without duplicating execution logic or changing behavior.

What is a legacy style alias used for in style-authoring pipelines?▼

A legacy style alias is used for migration and compatibility maintenance in style-authoring pipelines. It applies prompt aliasing to ensure older documentation referencing previous skill names continues to function correctly.

Does the styleauthor alias contain its own execution logic for style evolution?▼

No, the styleauthor alias does not contain separate execution logic. It remains thin and directly follows shared style-evolve workflow policies and guides to ensure consistent processing behavior.

When do I need to use prompt aliasing for workflow compatibility?▼

You need prompt aliasing for workflow compatibility when older automation pipelines reference legacy skill names. It helps teams upgrade platforms without immediately rewriting all prompts, scripts, or references.

How do I update style-evolve workflows while maintaining backwards compatibility?▼

To update workflows while maintaining backwards compatibility, apply the shared style-evolve workflow policies. This approach ensures consistency across the platform while keeping the legacy alias functional for older references.

Are there limitations to using a legacy alias for style-evolve migration?▼

The main limitation is that the alias must remain thin and free of separate execution logic. It strictly follows the shared style-evolve workflow policies, meaning any new logic must be implemented in the core workflow, not the alias.

Related Skills

Explore More Product & Management Skills→
ulises-jeremiasulises-jeremias
2

workflow-client-bootstrap

Alias deprecated skill names to updated versions for workflow continuity.

Community
Basic
fnsalinasfnsalinas
1

game-art

Coordinate art direction, asset pipelines, and animation workflows for game development.

Community
Intermediate
wadebeewadebee
2

shimmy-tool-jq

Guide jq Shimmy tool maintenance with version checks and container execution rules.

Community
Intermediate
drhazemibclcdrhazemibclc

workflows-work

Redirect deprecated /workflows:work alias to /ce:work command.

Community
Basic