Markstream Angular
Developmentmarkstream-angularMarkstream Angular is an Agent Skill for development published in the Simon-He95/markstream-vue repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Integrate markstream-angular into an Angular app. Use when Codex needs standalone component imports, signal-based examples, CSS wiring, custom HTML tags or customComponents setup, or optional peer integration in an Angular repository.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Simon-He95/markstream-vue/blob/HEAD/.agents/skills/markstream-angular/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/markstream-angular, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Markstream Angular
Use this skill when the host app is Angular and the task is to adopt the Angular package cleanly.
Workflow
- Confirm the repo is Angular.
- Install
markstream-angularplus only the requested optional peers. - Import
markstream-angular/index.cssfrom the app shell.- Add
katex/dist/katex.min.csswhen math is enabled.
- Add
- Prefer standalone Angular integration.
- Use
MarkstreamAngularComponentinimportsand keep examples signal-friendly.
- Use
- Start with
[content].- For streaming AI chat, keep
[content]and use built-in smooth streaming first.[smoothStreaming]="'auto'"is the default and activates when[typewriter]="true"or[maxLiveNodes]="0".[typewriter]only controls the blinking cursor and defaults tofalse.[fade]controls node enter and streamed-text fade animations and defaults totrue.
- Streaming vs recovering history: in chat UIs the same component starts streaming and later switches to history when
[final]="true".- Streaming:
[smoothStreaming]="'auto'",[fade]="false",[typewriter]="true". Smooth pacing handles gradual appearance; fade would flicker. - Recovering history:
[smoothStreaming]="false",[fade]="true",[typewriter]="false". Content is already complete — pacing would slow it down, but fade gives a polished entry animation. - Dynamic switch:
[smoothStreaming]="isStreaming ? 'auto' : false",[fade]="!isStreaming".
- Streaming:
- Use
[final]for end-of-stream state; final parsing is gated until visible content catches up when smooth streaming is active. - Move to
nodes+finalonly for worker-preparsed content, shared AST stores, or custom AST control. - Remember that
[htmlPolicy]now defaults to'safe', and Mermaid strict mode is on by default through[mermaidProps].
- For streaming AI chat, keep
- Use
[customHtmlTags]and[customComponents]for trusted tag workflows. - Validate with the smallest useful Angular dev or build command.
Default Decisions
- Standalone Angular first, NgModule-era patterns only when the repo still depends on them.
- Treat the cursor as opt-in (
typewriter=falseby default), but keep fade animations enabled by default (fade=true). - Keep optional peers minimal and explicit.
- Keep
[htmlPolicy]="'safe'"and Mermaid strict mode unless the task is preserving trusted legacy rendering. - If a trusted surface needs broader old behavior, opt out locally with
[htmlPolicy]="'trusted'"and[mermaidProps]="{ isStrict: false }", and document that trust boundary.
Useful Doc Targets
docs/guide/angular-quick-start.mddocs/guide/angular-installation.mddocs/guide/playground.mddocs/guide/troubleshooting.md