ssr
- Repo stars 779
- License Apache-2.0
- Author updated Live
- Author repo spartacus
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @SAP · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: ssr
description: Use this skill when working with Spartacus Server-Side Rendering (SSR). Trigger when the user me…
category: engineering
runtime: Node.js
---
# ssr output preview
## PART A: Task fit
- Use case: Use this skill when working with Spartacus Server-Side Rendering (SSR). Trigger when the user mentions SSR engine development, SSR E2E tests, server-side rendering issues, hydration problems, or needs to run SSR-related commands like 'npm run test:ssr' or 'npm run build:ssr'. Also trigger when working with files in 'core-libs/setup/ssr' or 'projects/ssr-tests/'..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Directory Structure / Commands” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use this skill when working with Spartacus Server-Side Rendering (SSR). Trigger when the user mentions SSR engine development, SSR E2E tests, server-side rendering issues, hydration problems, or needs to run SSR-related commands like 'npm run test:ssr' or 'npm run build:ssr'. Also trigger when working with files in 'core-libs/setup/ssr' or 'projects/ssr-tests/'.”.
- **02** When the source has headings, the agent prioritizes “Directory Structure / Commands” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Directory Structure / Commands”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: ssr
description: Use this skill when working with Spartacus Server-Side Rendering (SSR). Trigger when the user me…
category: engineering
source: SAP/spartacus
---
# ssr
## When to use
- Use this skill when working with Spartacus Server-Side Rendering (SSR). Trigger when the user mentions SSR engine deve…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Directory Structure / Commands” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "ssr" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Directory Structure / Commands
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Spartacus SSR Development
This skill covers Server-Side Rendering (SSR) development and testing.
Directory Structure
| Path | Purpose |
|---|---|
core-libs/setup/ssr |
Custom Angular SSR engine |
projects/ssr-tests/ |
E2E SSR tests (Node) |
Commands
# Unit test SSR lib (Jest)
nx run setup:test
# E2E SSR (requires special build first)
npm run build:ssr:local-http-backend # Build prerequisite - must run first
npm run test:ssr # Run SSR E2E tests
Decide Fit First
Design Intent
How To Use It
Boundaries And Review