Borrowing it
Nothing to install: this file belongs to wghglory/ngx-lift-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wghglory/ngx-lift-workspace/main/.agents/skills/lift-design/SKILL.mdgit clone --depth 1 https://github.com/wghglory/ngx-lift-workspaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wghglory/ngx-lift-workspace/lift-design)<a href="https://agentmods.dev/skills/wghglory/ngx-lift-workspace/lift-design"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/lift-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wghglory/ngx-lift-workspace/lift-design"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/lift-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.00474 |
| Opus 5.5 | $0.00015 | $0.00190 |
| Sonnet 5.5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
lift-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Design library behavior
Use the repository's development workflow as the canonical acceptance policy. Read the relevant existing design spec and current source first. The component roadmap defines Angular 21 delivery and the deferred platform upgrade.
- Identify the actual consumer use cases and current gaps. Inspect Clarity and current primary documentation/source from Angular Material, NG-ZORRO and relevant React libraries. Record specific adopt/adapt/reject decisions.
- Create or update the spec under
docs/design/ngx-lift/ordocs/design/clr-lift/using the template. Preserve the existing canonical spec when one exists. Include goals, non-goals, acceptance use cases, minimal/advanced examples, failure states and compatibility. - Apply the form contract to value controls. For display, navigation and utilities, explain the relevant integration instead of adding an artificial form value.
- Present the draft/API changes for review before implementation unless explicit approval already covers that scope. Keep proposal status and unavailable exports clear. On a design-only request, stop after producing the reviewable docs.
- After approval, implement functional increments and satisfy the workflow's demos, localization, tests, accessibility, lifecycle, performance and installed-consumer gates. Update the spec with actual evidence.
Read documentation standards when editing demo pages. Use the local nx-workspace skill to discover targets and the manifest/command guide for actual commands. Scale validation to the change; do not run component suites for a documentation-only draft or claim planned tests passed.
Completion means the requested scope is concrete and reviewable: either a draft with unresolved decisions stated, or an approved implementation with acceptance evidence and remaining external gates reported. Merge/publication require their own authorization and evidence. This skill does not create that authorization.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed 1584d4d05043
- 4d ago First seen · 34 lines · 38 tokens per session scan A cfb803659e44
lift-design is a skill published in the GitHub repository wghglory/ngx-lift-workspace (7 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 474 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…