AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Ui Ux Page Scoping

skill-evolplus-talos-ui-ux-page-scoping · by evolplus

Mandatory Step 0 for every UI/UX Designer mode. Resolve one Figma page as the scoped root before reading or writing Figma, update only the SRS page-scope fields when resolution is needed, and record the page Node ID/name in every UI/UX artifact so Figma operations do not walk brainstorm, archive, or Foundation pages by accident.

↗ Repository
— No reviews yet
0 installs
45 views
0.0% view→install

Install

$ agentstack add skill-evolplus-talos-ui-ux-page-scoping

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-evolplus-talos-ui-ux-page-scoping)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ui Ux Page Scoping? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

UI/UX Page Scoping

Use

Use this skill at the start of every UI/UX Designer dispatch mode:

  • extract
  • map
  • create
  • import
  • revise
  • incorporate

A Figma file has multiple pages. The kit scopes every read/write to one page per file so design extraction, mapping, and handoff do not mix project screens with drafts, archives, or the Foundation page.

Inputs

  • Dispatch Figma URL or the SRS ## Design References rows.
  • docs/SRS.md §3.4.1 fields:
  • Figma-File-URL
  • Figma-Design-Page-Node-ID
  • Figma-Design-Page-Name
  • Figma MCP read access.

Outputs

  • A resolved page Node ID used as the root for every later Figma operation.
  • Optional SRS §3.4.1 update limited to Figma-Design-Page-Node-ID and Figma-Design-Page-Name.
  • Page-scope metadata in the mode artifact:
  • Figma-Design-Page-Node-ID
  • Figma-Design-Page-Name

Procedure

  1. Read the Figma URL and the paired Figma-Design-Page-Node-ID / Figma-Design-Page-Name from SRS §3.4.1.
  2. If the SRS has UI requirements and the page field is missing or empty, halt with NEEDS_CONTEXT. Ask for the Figma page to use. Do not inspect every page to guess.
  3. Resolve the captured value:
  • PAGE node (CANVAS / PAGE) -> use it as the root.
  • FRAME or SECTION node -> walk up to the containing PAGE, then update the SRS page fields.
  • PAGE NAME string -> query available pages, resolve an exact case-insensitive match, then update the SRS page fields. If no unique match exists, halt with NEEDS_CONTEXT and list the page names.
  1. Scope every later Figma read/write to the subtree under the resolved page Node ID.
  2. Record the resolved page ID/name in the artifact produced by the mode.
  3. When a mode writes to Figma (create or revise), create or update project screens only inside the scoped page. The Foundation page remains governed by design-system-author.

Hard Rules

  • Never walk all pages of a Figma file for project screen work.
  • Never choose a page by intuition or by first page ordering.
  • Never modify SRS body content from this skill. Only the page-scope fields may be updated.
  • Never write project screens to the Foundation page unless the dispatch is explicitly about Foundation content.
  • Every downstream UI/UX artifact must carry the resolved page Node ID and page name.

References

  • .claude/skills/figma-requirements-extraction/
  • .claude/skills/figma-srs-mapping/
  • .claude/skills/figma-design-handoff/
  • .claude/skills/figma-canvas-layout/

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Content & Media