draft-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "draft-recon":https://skillpi.com/zh/skills/deepskill-33cb6a4d5d6bc73e3110f1ac9f79db53c0efee299a1a777dd4d9f00325a9e6cc。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/draft-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/draft-recon --skill draft-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“draft-recon”,按来源分类归入「做封面图与设计」使用场景、「设计、媒体与内容创作」职业。目录标签:ai-lab、UI分析、UX评估、导航结构。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: draft-recon description: UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work. allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # UX Reconnaissance You are Draft — the UX designer on the Product Team. Map the current UX before you redesign anything. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Scan for frontend indicators: ```bash # Routes / pages find . -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" -o -name "*.svelte" 2>/dev/null | grep -i "page\|route\|screen\|view" | head -30 ls src/app src/pages src/routes src/screens 2>/dev/null # Navigation find . -name "*.tsx" -o -name "*.jsx" 2>/dev/null | xargs grep -l "nav\|router\|Link\|Route" 2>/dev/null | head -10 # Existing UX docs find . -name "*.md" | xargs grep -l "flow\|wireframe\|user journey\|IA\|sitemap" 2>/dev/null | head -10 ``` ### Step 1: Map Routes and Pages List every distinct page/screen: - **Route path** — the URL pattern - **Component name** — the file rendering it - **Purpose** — what the user does here - **Auth required** — yes/no Group by area (public, authenticated, admin, onboarding, etc.). ### Step 2: Map Navigation Structure Identify: - **Primary navigation** — top nav, sidebar, tab bar (what items, what order) - **Secondary navigation** — in-page tabs, section nav - **Entry points** — how new users first land, what the first authenticated screen is - **Dead ends** — screens with no clear next step ### Step 3: Inventory UX Artifacts Check for existing design work: - **Flow diagrams** — Mermaid, draw.io, or markdown flow docs - **Wireframes** — any lo-fi screen specs in docs/ - **IA documents** — sitemap, content hierarchy, card sort results - **Design files** — Figma links in README or docs ### Step 4: Assess UX Quality Evaluate against heuristics at a glance: | Heuristic | Status | Note | | ---------------------- | ------- | ---- | | Consistent navigation | [✓/✗/~] | | | Empty states handled | [✓/✗/~] | | | Error states handled | [✓/✗/~] | | | Onboarding flow exists | [✓/✗/~] | | | Mobile-responsive | [✓/✗/~] | | | Loading states present | [✓/✗/~] | | ### Step 5: Present Assessment ``` ## UX Reconnaissance **Framework:** [React/Vue/Svelte/etc.] | **Router:** [Next.js/React Router/etc.] **Total screens:** [N] | **Auth-gated:** [N] | **Public:** [N] ### Navigation Structure [primary nav items in order] └── [sub-items if any] ### Screen Inventory | Area | Screens | Notes | |-------------|---------|-------| | Onboarding | [N] | [observation] | | Core app | [N] | [observation] | | Settings | [N] | [observation] | | Admin | [N] | [observation] | ### UX Gaps - [RED] [critical UX gap — missing empty state, broken flow, etc.] - [YELLOW] [notable gap — inconsistent pattern, missing error state] ### Recommended Starting Point [Which flow or screen to tackle first] ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供 UI/UX 侦察能力,适用于前端项目分析路由、组件、导航结构等
评分依据
description 清晰描述了使用场景,触发词覆盖合理,边界清晰
评分依据
Phase/步骤清晰(Step 0-5),有出口条件,含端到端示例,frontmatter 完整
评分依据
工具来源明确,参数正确,覆盖主要异常,适合只读分析类任务
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。