--- name: bookmark-analyzer-f3d5a066fcdd description: Use when analyzing Bookmark Vault codebase comprehensively from multiple dimensions simultaneously (component structure, data flow, type coverage). context: fork allowed-tools: Read, Grep, Glob --- # Bookmark Analyzer Analyzes Bookmark Vault using isolated context forks for three analysis areas simultaneously, then merges findings into a unified report. ## When to Use - Comprehensive codebase review needed - Analyzing multiple dimensions: architecture, data flow, type safety - Need isolated findings per perspective (prevents cross-contamination of analysis) - Building reports that synthesize findings across layers ## Core Pattern: Isolation → Analysis → Synthesis ``` Request: "Analyze bookmark vault comprehensively" ↓ FORK 1: Component Structure Analysis ├─ Tools: Glob components/, Grep for React exports ├─ Analysis: Count, hierarchy, reusability └─ Output: Structured findings with specific metrics FORK 2: Data Flow Analysis (runs in parallel) ├─ Tools: Grep useBookmarks, hooks/, lib/storage ├─ Analysis: Trace state, prop drilling, hook dependencies └─ Output: Flow diagrams, path analysis, metrics FORK 3: Type Coverage Analysis (runs in parallel) ├─ Tools: Read lib/types.ts, lib/validation.ts ├─ Analysis: Interface coverage, Zod schemas, alignment └─ Output: Coverage score, gaps, alignment matrix SYNTHESIZE: Merge three outputs ├─ Combine findings preserving section structure ├─ Identify cross-section implications ├─ Create unified recommendations └─ Return final report ``` ## Analysis Areas ### Fork 1: Component Structure Analysis **Objective:** Quantify component inventory and relationships **Tasks:** 1. Count total components by category (UI primitives, feature modules, etc.) 2. Map parent-child relationships (component tree) 3. Identify high-reuse components 4. Analyze size distribution (lines per component) **Key Files:** - `components/ui/` - UI primitives - `components/bookmarks/` - Feature modules - `components/vault/`, `components/settings/`, `components/sync/` - `components/spaces/`, `components/theme/`, `components/auth/` **Output Format:** ``` ## Component Structure Analysis ### Inventory - Total components: [count] - UI primitives: [count] - Feature modules: [count] - [Other categories] ### Hierarchy [Component tree showing relationships] ### Reusability - High-reuse components: [list with usage count] - Reuse score: [percentage] ### Size Distribution - Components < 100 lines: [count] - Components 100-200 lines: [count] - Components 200+ lines: [count] ### Key Findings [Specific observations about structure quality, issues] ``` ### Fork 2: Data Flow Analysis **Objective:** Trace how bookmark data moves through the system **Tasks:** 1. Identify data sources: localStorage, Context, Zustand stores 2. Trace state flow: storage → hooks → components 3. Map prop drilling chains (count depth, props per component) 4. Document hook dependencies and interconnections 5. Identify refresh mechanisms and data sync patterns **Key Files:** - `hooks/useBookmarks.ts` - Main state hook - `hooks/useSyncEngineUnified.ts` - Sync orchestration - `lib/storage.ts` - localStorage access - `stores/vault-store.ts`, `stores/settings-store.ts` - Zustand stores **Output Format:** ``` ## Data Flow Analysis ### Flow Paths - Storage layer: [what stores data] - State management: [useBookmarks context flow] - UI consumption: [component data flow] ### Prop Drilling Analysis - Max depth: [levels] - Components with 8+ props: [list] - Average props per component: [number] ### Hook Dependencies - [Hook name]: Depends on [other hooks/stores] - [Circular dependency check results] ### Data Refresh Mechanisms - [Pattern 1]: [description] - [Pattern 2]: [description] ### Issues Found [Specific prop drilling bottlenecks, refresh issues] ### Key Findings [Assessment of data flow quality, performance implications] ``` ### Fork 3: Type Coverage Analysis **Objective:** Assess TypeScript safety and validation completeness **Tasks:** 1. Verify TypeScript configuration (strict mode enabled) 2. Count and categorize types/interfaces defined 3. Check Zod schema coverage vs. interface definitions 4. Audit function signatures for proper typing 5. Identify any `any` type usage 6. Validate component prop interfaces **Key Files:** - `lib/types.ts` - Core domain types - `lib/validation.ts` - Zod schemas - `components/**/*.tsx` - Component prop interfaces - `hooks/**/*.ts` - Hook return types - `tsconfig.json` - TS configuration **Output Format:** ``` ## Type Coverage Analysis ### Configuration - TypeScript strict mode: [enabled/disabled] - Strict flags: [list if enabled] ### Type Definitions - Total interfaces: [count] - Total type aliases: [count] - Exported core types: [count with list] ### Validation Schemas - Total Zod schemas: [count] - Schema coverage: [percentage with details] ### Schema-Interface Alignment | Type | Interface | Schema | Alignment | | --- | --- | --- | --- | | [Type name] | ✓/❌ | ✓/❌ | [Status] | ### Coverage Metrics - Hook return types: [percentage typed] - Component props: [percentage typed] - Function signatures: [percentage typed] - `any` type usage: [count, locations if found] ### Issues Found [Missing schemas, untyped functions, alignment gaps] ### Key Findings [Overall type safety score, gaps, recommendations] ``` ## Output Format (Synthesis) Return combined analysis as single structured report: ```markdown # Bookmark Vault Comprehensive Analysis ## Component Structure Analysis [Fork 1 findings] ## Data Flow Analysis [Fork 2 findings] ## Type Coverage Analysis [Fork 3 findings] ## Cross-Section Implications [Observations connecting multiple areas] ## Recommendations (Prioritized) 1. [Specific, actionable recommendation] 2. [Specific, actionable recommendation] 3. [Specific, actionable recommendation] ## Overall Assessment Score - Component Architecture: [/10] - Data Flow: [/10] - Type Safety: [/10] - OVERALL: [/10] ``` ## Common Issues to Watch | Issue | Signal | Location | |---|---|---| | Prop drilling bottleneck | Component receives 8+ props | Check if can extract to hook | | Missing schema | Type defined but no validation | Add Zod schema | | Circular dependency | Hook A depends on B, B depends on A | Refactor to separate concerns | | Type gaps | `any` found in code | Replace with explicit type | | Untyped component | Props interface missing | Add `interface XyzProps` | | Sync complexity | Single hook > 400 lines | Consider splitting responsibilities | ## Analysis Verification Checklist - [ ] Fork 1: Component count verified via Glob - [ ] Fork 1: Parent-child tree complete (spot-check 5 components) - [ ] Fork 2: Data flow traced from storage to UI (end-to-end) - [ ] Fork 2: Prop drilling documented with specific component paths - [ ] Fork 3: TypeScript config verified (read tsconfig.json) - [ ] Fork 3: Zod schemas counted and compared to interfaces - [ ] Synthesis: All three areas represented in final report - [ ] Recommendations: Each is actionable and specific ## Red Flags - STOP and Reconsider These indicate analysis might be incomplete or context-forking failed: | Red Flag | What to Do | Rationalization to Block | |---|---|---| | "It seems like..." without verification | Stop. Find specific file/line numbers. | "I can estimate without precise data" | | Only 1-2 findings per area | Incomplete. Each area should have 3-5 findings minimum. | "Some areas just don't have much" | | Generic observations ("code is clean") | Incomplete. Need specific metrics and evidence. | "Quality is obvious without details" | | Skipping one of three areas | **CRITICAL ERROR**. All three forks must produce findings. | "Component analysis covers everything" | | Merged findings with no section breaks | Failed synthesis. Keep areas separate, then synthesize. | "Combining saves time on writing" | | Recommendations without evidence | Invalid. Each recommendation must reference specific finding. | "These are best practices anyway" | | No component count or metric numbers | Incomplete Fork 1. Requires: total count, size distribution. | "Exact numbers don't matter much" | | No prop drilling analysis or depth number | Incomplete Fork 2. Requires: depth count, examples with paths. | "Prop drilling isn't really an issue" | | No schema-interface alignment table | Incomplete Fork 3. Requires: coverage %, specific gaps. | "Type safety is obvious from inspection" | | Single report without three sections | Context-forking failed. Must show Fork 1, 2, 3 results separately first. | "One big report is cleaner" | | No "Cross-Section Implications" section | Failed synthesis step. Findings must connect across forks. | "Each area stands alone" | --- ## Rationalization Blocking (Discipline Pattern) **The core pattern you're protecting against:** "I can combine the three analyses into one big report faster" **Reality:** This violates the isolation principle. Fork results MUST be separated first. **Steps to combat this:** 1. **Even if rushing**: Present Fork 1 findings first, Fork 2 second, Fork 3 third 2. **Even if fork had no major issues**: Include "Key Findings" section per fork showing isolation maintained 3. **Even if synthesis seems obvious**: Write explicit "Cross-Section Implications" - don't skip this step 4. **Even if one area seems small**: Include it with any findings found (minimum: configuration details) **Exception:** None. Always separate, then synthesize. --- ## Success Criteria ✓ **Report includes all three analysis areas with structured section breaks** ✓ **Each area has 3+ specific findings with metrics or line references** ✓ **Fork isolation maintained**: Findings organized by Fork 1 → Fork 2 → Fork 3 → Synthesis** ✓ **Cross-section implications section present and non-empty** ✓ **Recommendations are actionable and tied to specific findings with file paths** ✓ **Overall assessment score provided with supporting evidence** ✓ **Verification checklist completed and all items checked** ✓ **No vague observations without data backing them** ✓ **No recommendations without line number or file reference** ✓ **Schema-interface alignment has actual percentages, not estimates** --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/bookmark-analyzer/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/bookmark-analyzer/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Development & Engineering, Product Management Roles: Backend Developer, Data Analyst, Frontend Developer, Product Manager, QA / Test Engineer Specialties: Backend, Frontend, Testing Tools: Glob, Grep, Read Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 1b1c1b74292b3d1946ed95d542fe20ca1f9c15019965c9acd73ec6044e9a845b