Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    urdesigner

    1

    Code-grounded product design and estimation that reads your source code to generate specs, epics, and stories.

    Free

    Security scanned
    urdesigner

    urdesigner

    Example session with this skill installed

    /spec Let users share an item read-only with another user by email

    • Read your context and instructions
    • Compiled the urdesigner
    • Generated the document

    Ran /spec on fastapi/full-stack-fastapi-template. Read 12 files, then saved the spec to docs/specs/2026-11-13-read-only-item-sharing.md.


    Spec: Read-Only Item Sharing

    Files reviewed: backend/app/models.py, backend/app/api/routes/items.py, backend/app/api/deps.py, backend/app/crud.py, backend/app/api/routes/users.py, backend/app/alembic/versions/ (5 revisions, head fe56fa70289e), backend/tests/api/routes/test_items.py, backend/tests/utils/item.py, frontend/src/routes/_layout/items.tsx, frontend/src/components/Items/columns.tsx, frontend/src/components/Items/ItemActionsMenu.tsx, scripts/generate-client.sh
    Date: 2026-11-13

    Summary

    Let an item's owner share it, read-only, with another registered user by email. The recipient sees shared items in a separate "Shared with me" view. Only the owner (or a superuser) can edit, delete or manage the item's shares.

    Background

    No CLAUDE.md or STRATEGY.md in the repo. Inferred from code: items are strictly single-owner today (Item.owner_id, enforced per-endpoint in items.py), so this is the first multi-user access path in the app.

    Technical Architecture

    Data model — new link table in models.py, following the existing Item conventions (UUID PK, get_datetime_utc timestamps, ondelete="CASCADE" FKs):

    FieldTypeNotes
    idUUIDPK
    item_idUUID → item.idondelete="CASCADE"
    user_idUUID → user.idondelete="CASCADE" (recipient)
    created_atdatetime

    Unique constraint on (item_id, user_id). New Alembic revision with down_revision = "fe56fa70289e". New table only — no backfill.

    API (all under the existing /items router):

    MethodPathWho
    POST/items/{id}/shares body {email}owner / superuser
    GET/items/{id}/sharesowner / superuser
    DELETE/items/{id}/shares/{user_id}owner / superuser, or the recipient (leave share)
    GET/items/shared-with-meany active user

    read_item (GET /items/{id}) must also allow a user with a share row. update_item and delete_item stay owner-only — unchanged.

    Permission logic — the check not current_user.is_superuser and item.owner_id != current_user.id is copied in read_item, update_item and delete_item. Extract get_item_for_read() / get_item_for_write() helpers so the new read path can't drift from the write path.

    Response shape — ItemPublic exposes owner_id only. The shared view needs a human-readable owner, so add owner_full_name / owner_email to a new SharedItemPublic instead of widening ItemPublic.

    Frontend — regenerate the client via scripts/generate-client.sh (OpenAPI → @hey-api/openapi-ts). Add a "Share" entry to ItemActionsMenu.tsx and a "Shared with me" tab or route next to _layout/items.tsx.

    User Flows

    Primary path (owner): Items → row menu (⋮) → Share → enter email → Share → recipient appears in "Shared with" list with a remove button.

    Primary path (recipient): Items → "Shared with me" → sees title, description, owner → can open, cannot edit or delete → can "Leave".

    Error states:

    • Email not registered → see Risk 1; response must not confirm whether the account exists.
    • Sharing with yourself → 400, inline message.
    • Already shared → idempotent; return the existing share, no duplicate.
    • Owner deletes item → share rows cascade; item disappears from recipient's list.

    Edge cases: recipient deactivated (is_active=False is rejected by get_current_user, so they simply can't log in); superuser sees all items already via read_items — decide whether shares are listed for them.

    Technical Risks

    #RiskRatingEvidence
    1Share-by-email becomes a user-enumeration oracleHIGHcrud.authenticate uses DUMMY_HASH to prevent timing leaks — the team clearly treats enumeration as a threat. read_users is superuser-only, so there is no sanctioned user lookup today.
    2Permission check duplicated in 3 handlers; adding a 4th variant invites a bypassMEDIUMitems.py L56, L89, L109
    3ItemActionsMenu renders Edit/Delete for every row; reused for shared rows it would show actions that 403MEDIUMcolumns.tsx actions column
    4MigrationLOWNew table only, no live-data rewrite
    5Pagination/count for shared listLOWMirror read_items skip/limit + func.count() pattern

    Design Constraints

    • Reuse existing primitives: DropdownMenu in ItemActionsMenu, DataTable + columns for the shared list, the empty-state block in items.tsx (copy: "Nothing has been shared with you yet").
    • Shared rows must not render Edit/Delete — use a separate column set, not a hidden button.
    • Share dialog follows AddItem/EditItem dialog patterns.

    Acceptance Criteria

    • Owner can share an item with a registered user by email; recipient sees it under "Shared with me".
    • Recipient can GET /items/{id} (200) but PUT/DELETE return 403.
    • Non-owner, non-recipient gets 403 on read, as today.
    • Sharing the same item with the same user twice creates one row.
    • Deleting the item or either user deletes the share rows (cascade).
    • Share endpoint response is identical for registered and unregistered emails (Risk 1).
    • Shared rows show no Edit/Delete actions in the UI.
    • New tests in tests/api/routes/test_items.py mirror the existing *_not_enough_permissions cases for every new endpoint.

    Open Questions

    #QuestionOwnerBlocks
    1NEEDS SPIKE: Unregistered email — silently accept (store pending invite) or always return a generic "If this user exists, they now have access"? utils.py already has send_email + templates, so an invite email is feasible — confirm SMTP is configured in all environments before choosing.BothYes
    2Should superusers see share lists for all items?TechnicalNo
    3Notify the recipient by email when something is shared?UXNo
    4Is read-only enough, or is "can edit" expected within a quarter? (Affects whether to add a role column now.)UXNo

    Out of Scope

    • Edit permissions for recipients
    • Sharing with groups/teams or via public link
    • Invites for users who haven't registered
    • Activity/audit log of shares

    Next steps: resolve open question #1 (NEEDS SPIKE), then run /epic docs/specs/2026-11-13-read-only-item-sharing.md.

    items.tsx

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most AI planning output sounds confident but describes an architecture that doesn't exist. urdesigner works the other way around: senior engineering personas read the relevant files first, cite what they read, and mark anything they can't verify as NEEDS SPIKE instead of guessing.

    What it does

    • Spec — A Staff Engineer and a Design Lead review the code together and produce one combined technical + UX spec: architecture, data flow, risks (LOW/MEDIUM/HIGH), user flows, acceptance criteria, open questions.
    • Epics — Breaks a spec into 3–7 independently deliverable epics, ordered risk-first, with dependencies, sizes and a sequencing diagram.
    • Stories — Decomposes an epic into user stories with Given/When/Then acceptance criteria, Definition of Done, technical notes and readiness flags.
    • Estimate — Backend, Frontend, QA and DevOps personas estimate independently; a 2x divergence triggers a discussion round; the consensus comes with confidence and risk flags.

    Every artifact is saved to a dated file under docs/ so your planning persists across sessions.

    Planning only — it never modifies your application code.

    Example prompts

    • "Spec out adding SSO login to this app"
    • "Break docs/specs/2026-11-13-sso.md into epics"
    • "Write stories for the 'Session migration' epic"
    • "Estimate the SSO epics"

    Open source (MIT): https://github.com/alisuleymantopuz/urdesigner

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Product Management.

    Does not write or modify application code. Requires a local codebase to be accessible for context. Estimates are focused on engineering effort, not business timelines.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files

    File Scopes

    docs/**

    Reads your codebase to ground specs and estimates. Writes only its own planning documents to dated files under docs/ (specs, epics, stories, estimates). Never modifies application code.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    Unlike generic prompts, urdesigner enforces a "read-before-write" workflow that analyzes your actual folder structure and architectural patterns, ensuring generated specs are technically feasible rather than idealized or "hallucinated."

    The skill is optimized for CLI-based and IDE-integrated agents like Claude Code, Cursor, and Gemini CLI that have permission to read local files and write to your directory.

    urdesigner provides multi-persona estimates (Backend, Frontend, QA, and DevOps) and automatically flags high-risk tasks with a `NEEDS SPIKE` label when it encounters architectural territory it hasn't seen in your codebase.

    No, urdesigner is strictly a design and planning tool; it reads your code to understand constraints but will only output documentation, specs, and stories to your `docs/` folder without modifying your source code.

    Simply import the skill into your preferred AI agent and point it toward your project's root directory so it can begin the architectural analysis required for speccing.

    New in Product Management

    Free