[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4RM60Z0B06MVD3GGVZZV5":3,"skill-same:01M6C4RM60Z0B06MVD3GGVZZV5":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6C4RM60Z0B06MVD3GGVZZV5","research",null,"Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.","hungtrandigital\u002FResidentOne","hungtrandigital","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25002353?v=4","01M6C49HS2DVC9NWE17SC8HMSJ","01M6C4NEXA9Y9VXK786C1JBATW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fresearch\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[5,23,24,25,26,27],"secure","plan","analyze","technical","use","2026-11-10 10:12:30",false,"---\nname: research\ndescription: Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.\nlicense: MIT\n---\n\n# Research\n\n## Research Methodology\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### Phase 1: Scope Definition\n\nFirst, you will clearly define the research scope by:\n- Identifying key terms and concepts to investigate\n- Determining the recency requirements (how current must information be)\n- Establishing evaluation criteria for sources\n- Setting boundaries for the research depth\n\n### Phase 2: Systematic Information Gathering\n\nYou will employ a multi-source research strategy:\n\n1. **Search Strategy**:\n   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p \"...your search prompt...\"` (timeout: 10 minutes).\n   - If `gemini` bash command is not available, fallback to `WebSearch` tool.\n   - Run multiple `gemini` bash commands or `WebSearch` tools in parallel to search for relevant information.\n   - Craft precise search queries with relevant keywords\n   - Include terms like \"best practices\", \"2024\", \"latest\", \"security\", \"performance\"\n   - Search for official documentation, GitHub repositories, and authoritative blogs\n   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)\n   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.\n\n2. **Deep Content Analysis**:\n   - When you found a potential Github repository URL, use `docs-seeker` skill to find read it.\n   - Focus on official documentation, API references, and technical specifications\n   - Analyze README files from popular GitHub repositories\n   - Review changelog and release notes for version-specific information\n\n3. **Video Content Research**:\n   - Prioritize content from official channels, recognized experts, and major conferences\n   - Focus on practical demonstrations and real-world implementations\n\n4. **Cross-Reference Validation**:\n   - Verify information across multiple independent sources\n   - Check publication dates to ensure currency\n   - Identify consensus vs. controversial approaches\n   - Note any conflicting information or debates in the community\n\n### Phase 3: Analysis and Synthesis\n\nYou will analyze gathered information by:\n- Identifying common patterns and best practices\n- Evaluating pros and cons of different approaches\n- Assessing maturity and stability of technologies\n- Recognizing security implications and performance considerations\n- Determining compatibility and integration requirements\n\n### Phase 4: Report Generation\n\n**Notes (AI Factory output locations):**\n- Prefer updating existing canonical files first (e.g., `1-ideas\u002Fmarket-research\u002Fsummaries.md`, `2-product-foundation\u002F2.2-product-backlog\u002Fbacklog.md`).\n- If a standalone report is necessary, it must be attached to an existing plan in `3-technical\u002F3.2-implementation\u002Fplans\u002F` (and may require @docs-guardian consultation before creating a new file).\n\nYou will create a comprehensive markdown report with the following structure:\n\n```markdown\n# Research Report: [Topic]\n\n## Executive Summary\n[2-3 paragraph overview of key findings and recommendations]\n\n## Research Methodology\n- Sources consulted: [number]\n- Date range of materials: [earliest to most recent]\n- Key search terms used: [list]\n\n## Key Findings\n\n### 1. Technology Overview\n[Comprehensive description of the technology\u002Ftopic]\n\n### 2. Current State & Trends\n[Latest developments, version information, adoption trends]\n\n### 3. Best Practices\n[Detailed list of recommended practices with explanations]\n\n### 4. Security Considerations\n[Security implications, vulnerabilities, and mitigation strategies]\n\n### 5. Performance Insights\n[Performance characteristics, optimization techniques, benchmarks]\n\n## Comparative Analysis\n[If applicable, comparison of different solutions\u002Fapproaches]\n\n## Implementation Recommendations\n\n### Quick Start Guide\n[Step-by-step getting started instructions]\n\n### Code Examples\n[Relevant code snippets with explanations]\n\n### Common Pitfalls\n[Mistakes to avoid and their solutions]\n\n## Resources & References\n\n### Official Documentation\n- [Linked list of official docs]\n\n### Recommended Tutorials\n- [Curated list with descriptions]\n\n### Community Resources\n- [Forums, Discord servers, Stack Overflow tags]\n\n### Further Reading\n- [Advanced topics and deep dives]\n\n## Appendices\n\n### A. Glossary\n[Technical terms and definitions]\n\n### B. Version Compatibility Matrix\n[If applicable]\n\n### C. Raw Research Notes\n[Optional: detailed notes from research process]\n```\n\n## Quality Standards\n\nYou will ensure all research meets these criteria:\n- **Accuracy**: Information is verified across multiple sources\n- **Currency**: Prioritize information from the last 12 months unless historical context is needed\n- **Completeness**: Cover all aspects requested by the user\n- **Actionability**: Provide practical, implementable recommendations\n- **Clarity**: Use clear language, define technical terms, provide examples\n- **Attribution**: Always cite sources and provide links for verification\n\n## Special Considerations\n\n- When researching security topics, always check for recent CVEs and security advisories\n- For performance-related research, look for benchmarks and real-world case studies\n- When investigating new technologies, assess community adoption and support levels\n- For API documentation, verify endpoint availability and authentication requirements\n- Always note deprecation warnings and migration paths for older technologies\n\n## Output Requirements\n\nYour final report must:\n1. Be saved as a markdown file with a descriptive filename in `.\u002Fplans\u002F\u003Cplan-name>\u002Freports\u002FYYMMDD-\u003Cyour-research-topic>.md`\n2. Include a timestamp of when the research was conducted\n3. Provide clear section navigation with a table of contents for longer reports\n4. Use code blocks with appropriate syntax highlighting\n5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)\n6. Conclude with specific, actionable next steps\n\n**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.\n**IMPORTANT:** In reports, list any unresolved questions at the end, if any.\n\n**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.","# Research\n\n## Research Methodology\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### Phase 1: Scope Definition\n\nFirst, you will clearly define the research scope by:\n- Identifying key terms and concepts to investigate\n- Determining the recency requirements (how current must information be)\n- Establishing evaluation criteria for sources\n- Setting boundaries for the research depth\n\n### Phase 2: Systematic Information Gathering\n\nYou will employ a multi-source research strategy:\n\n1. **Search Strategy**:\n   - Check if `gemini` bash command is available, if so, execute `gemini -m gemini-2.5-flash -p \"...your search prompt...\"` (timeout: 10 minutes).\n   - If `gemini` bash command is not available, fallback to `WebSearch` tool.\n   - Run multiple `gemini` bash commands or `WebSearch` tools in parallel to search for relevant information.\n   - Craft precise search queries with relevant keywords\n   - Include terms like \"best practices\", \"2024\", \"latest\", \"security\", \"performance\"\n   - Search for official documentation, GitHub repositories, and authoritative blogs\n   - Prioritize results from recognized authorities (official docs, major tech companies, respected developers)\n   - **IMPORTANT:** You are allowed to perform at most **5 researches (max 5 tool calls)**, user might request less than this amount, **strictly respect it**, think carefully based on the task before performing each related research topic.\n\n2. **Deep Content Analysis**:\n   - When you found a potential Github repository URL, use `docs-seeker` skill to find read it.\n   - Focus on official documentation, API references, and technical specifications\n   - Analyze README files from popular GitHub repositories\n   - Review changelog and release notes for version-specific information\n\n3. **Video Content Research**:\n   - Prioritize content from official channels, recognized experts, and major conferences\n   - Focus on practical demonstrations and real-world implementations\n\n4. **Cross-Reference Validation**:\n   - Verify information across multiple independent sources\n   - Check publication dates to ensure currency\n   - Identify consensus vs. controversial approaches\n   - Note any conflicting information or debates in the community\n\n### Phase 3: Analysis and Synthesis\n\nYou will analyze gathered information by:\n- Identifying common patterns and best practices\n- Evaluating pros and cons of different approaches\n- Assessing maturity and stability of technologies\n- Recognizing security implications and performance considerations\n- Determining compatibility and integration requirements\n\n### Phase 4: Report Generation\n\n**Notes (AI Factory output locations):**\n- Prefer updating existing canonical files first (e.g., `1-ideas\u002Fmarket-research\u002Fsummaries.md`, `2-product-foundation\u002F2.2-product-backlog\u002Fbacklog.md`).\n- If a standalone report is necessary, it must be attached to an existing plan in `3-technical\u002F3.2-implementation\u002Fplans\u002F` (and may require @docs-guardian consultation before creating a new file).\n\nYou will create a comprehensive markdown report with the following structure:\n\n```markdown\n# Research Report: [Topic]\n\n## Executive Summary\n[2-3 paragraph overview of key findings and recommendations]\n\n## Research Methodology\n- Sources consulted: [number]\n- Date range of materials: [earliest to most recent]\n- Key search terms used: [list]\n\n## Key Findings\n\n### 1. Technology Overview\n[Comprehensive description of the technology\u002Ftopic]\n\n### 2. Current State & Trends\n[Latest developments, version information, adoption trends]\n\n### 3. Best Practices\n[Detailed list of recommended practices with explanations]\n\n### 4. Security Considerations\n[Security implications, vulnerabilities, and mitigation strategies]\n\n### 5. Performance Insights\n[Performance characteristics, optimization techniques, benchmarks]\n\n## Comparative Analysis\n[If applicable, comparison of different solutions\u002Fapproaches]\n\n## Implementation Recommendations\n\n### Quick Start Guide\n[Step-by-step getting started instructions]\n\n### Code Examples\n[Relevant code snippets with explanations]\n\n### Common Pitfalls\n[Mistakes to avoid and their solutions]\n\n## Resources & References\n\n### Official Documentation\n- [Linked list of official docs]\n\n### Recommended Tutorials\n- [Curated list with descriptions]\n\n### Community Resources\n- [Forums, Discord servers, Stack Overflow tags]\n\n### Further Reading\n- [Advanced topics and deep dives]\n\n## Appendices\n\n### A. Glossary\n[Technical terms and definitions]\n\n### B. Version Compatibility Matrix\n[If applicable]\n\n### C. Raw Research Notes\n[Optional: detailed notes from research process]\n```\n\n## Quality Standards\n\nYou will ensure all research meets these criteria:\n- **Accuracy**: Information is verified across multiple sources\n- **Currency**: Prioritize information from the last 12 months unless historical context is needed\n- **Completeness**: Cover all aspects requested by the user\n- **Actionability**: Provide practical, implementable recommendations\n- **Clarity**: Use clear language, define technical terms, provide examples\n- **Attribution**: Always cite sources and provide links for verification\n\n## Special Considerations\n\n- When researching security topics, always check for recent CVEs and security advisories\n- For performance-related research, look for benchmarks and real-world case studies\n- When investigating new technologies, assess community adoption and support levels\n- For API documentation, verify endpoint availability and authentication requirements\n- Always note deprecation warnings and migration paths for older technologies\n\n## Output Requirements\n\nYour final report must:\n1. Be saved as a markdown file with a descriptive filename in `.\u002Fplans\u002F\u003Cplan-name>\u002Freports\u002FYYMMDD-\u003Cyour-research-topic>.md`\n2. Include a timestamp of when the research was conducted\n3. Provide clear section navigation with a table of contents for longer reports\n4. Use code blocks with appropriate syntax highlighting\n5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)\n6. Conclude with specific, actionable next steps\n\n**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.\n**IMPORTANT:** In reports, list any unresolved questions at the end, if any.\n\n**Remember:** You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.",{"name":5,"license":14,"description":7},"main","89c86fd97855e6925d9bc26192f1e911bcbbb291","0-agents\u002Fagents\u002Fskills\u002Fresearch","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne","https:\u002F\u002Fgithub.com\u002Fhungtrandigital","2025-12-15 11:00:17",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add hungtrandigital\u002FResidentOne --skill research",{"tool":45,"command":46},"bunx","bunx skills add hungtrandigital\u002FResidentOne --skill research",{"tool":48,"command":49},"pnpm","pnpm dlx skills add hungtrandigital\u002FResidentOne --skill research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fresearch\u002FSKILL.md",true,[],[54,80,108,131,145,151],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":28},"01M6C4SJJB90YSQZT2MTSN0GC5","web-frameworks","Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined\u002Ffilled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[61,62,63,64,65,66,27,67,68,69,70,71,72,73,74,75,76,77,78,79],"web frameworks","web","applications","parallel execution","up","router","monorepo","parallel","stack","projects","Next.js","execution","server","icons","packages","libraries","react","components","performance",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":94,"publishedAt":28},"01M6C4S5DJXAB94E33E98Y0KFW","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fui-styling\u002FSKILL.md",[86,89],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[95,96,97,98,99,100,63,101,102,103,78,104,105,106,107,27],"styling","ui","ui styling","user","Tailwind","first","shadcn","design systems","create","canvas","css","design","radix ui",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":28},"01M6C4S1SK4FH1200A3FBS7MVN","threejs","Build immersive 3D web experiences with Three.js - WebGL\u002FWebGPU library for scenes, cameras, geometries, materials, lights, animations, loaders, post-processing, shaders (including node-based TSL), compute, physics, VR\u002FXR, and advanced rendering. Use when creating 3D visualizations, games, interactive graphics, data viz, product configurators, architectural walkthroughs, or WebGL\u002FWebGPU applications. Covers OrbitControls, GLTF\u002FFBX loading, PBR materials, shadow mapping, post-processing effects (bloom, SSAO, SSR), custom shaders, instancing, LOD, animation systems, and WebXR.","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[110,115,116,117,118,119,27,120,63,121,122,123,124,125,62,126,127,128,129,130],"interactive","3D","data","visualizations","node","pbr","library","product","shaders","ssr","webgpu","webxr","webgl","Animation","graphics","gltf",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":28},"01M6C4RP0SV44MC0YCNME88W0Q","sequential-thinking","Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[138,27,139,140,141,142,143,144],"sequential thinking","work","analysis","hypothesis","verification","planning","tasks",{"skillNo":146,"name":143,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":28},"01M6C4RBZJRKX6H9CQ9ABECXX0","Use when you need to plan technical solutions that are scalable, secure, and maintainable.","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fplanning\u002FSKILL.md",[],[143,26,24,23,27],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":28},"01M6C4R7RZQW019J34AFS3K1GZ","payment-integration","Implement payment integrations with SePay (Vietnamese payment gateway with VietQR, bank transfers, cards) and Polar (global SaaS monetization platform with subscriptions, usage-based billing, automated benefits). Use when integrating payment processing, implementing checkout flows, managing subscriptions, handling webhooks, processing bank transfers, generating QR codes, automating benefit delivery, or building billing systems. Supports authentication (API keys, OAuth2), product management, customer portals, tax compliance (Polar as MoR), and comprehensive SDK integrations (Node.js, PHP, Python, Go, Laravel, Next.js).","https:\u002F\u002Fgithub.com\u002Fhungtrandigital\u002FResidentOne\u002Fblob\u002Fmain\u002F0-agents\u002Fagents\u002Fskills\u002Fpayment-integration\u002FSKILL.md",[],[158,159,160,27,161,162,119,163,164,71,165,166,167,122,168,169,170,171,172,173],"payment integration","integration","api","management","tax","integrations","laravel","saas","compliance","gateway","authentication","customer","implement","sdk","python","go"]