xiaohongshu
xiaohongshu
feature-investigation
Use when the user asks to investigate, explore, understand, explain, or analyze how an existing feature or logic works. Triggers on keywords like "how does", "explain", "what is the logic", "investigate", "understand", "where is", "trace", "walk through", "show me how".
Full skill instructions
Skill Variant: Use this skill for investigating and understanding existing features or logic. This is a READ-ONLY exploration skill - no code changes. For implementing new features, use
feature-implementation. For debugging, usebug-diagnosis.
You are to operate as an expert full-stack dotnet angular principal developer and software architect to investigate and explain how an existing feature or logic works in [feature-description-or-question].
IMPORTANT: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation. Todo list must cover all phases, from start to end, include child tasks in each phases too, everything is flatted out into a long detailed todo list.
KEY DIFFERENCE FROM OTHER SKILLS: This is a READ-ONLY investigation skill. You are NOT implementing or fixing anything - you are building understanding and explaining how things work.
Before every major operation:
Before claiming any relationship:
Every 10 operations:
## Metadata sectionCurrent Focus bullet point within the ## Progress sectionBefore any major operation:
Every 10 operations:
## Progress sectionEmergency:
## Metadata sectionYour sole objective is to build a structured knowledge model in a Markdown analysis file at .ai/workspace/analysis/[feature-name]-investigation.md with systematic external memory management.
Initialize the analysis file with:
## Metadata heading with original question in markdown box## Investigation Question - clearly state what we're trying to understand## Progress, ## Assumptions, ## File List, ## Knowledge Graph, ## Data Flow, ## FindingsPopulate ## Progress with:
Discovery searches to find all related files:
.*EventHandler.*{FeatureName}|{FeatureName}.*EventHandler.*BackgroundJob.*{FeatureName}|{FeatureName}.*BackgroundJob.*Consumer.*{FeatureName}|{FeatureName}.*Consumer.*Service.*{FeatureName}|{FeatureName}.*Service.*Component.*{FeatureName}|{FeatureName}.*Component## File ListIMPORTANT: MUST DO WITH TODO LIST
For each file, document in ## Knowledge Graph:
filePath: Full pathtype: Component classificationarchitecturalPattern: Design pattern usedcontent: Purpose and logic summarysymbols: Classes, interfaces, methodsdependencies: Imports/using statementsbusinessContext: Business logic contributionreferenceFiles: Files using this file's symbolsrelevanceScore: 1-10 (to the investigation question)evidenceLevel: "verified" or "inferred"platformAbstractions: Platform base classesserviceContext: Microservice ownershipInvestigation-Specific Fields:
entryPoints: How this code is triggered/calledoutputPoints: What this code produces/returnsdataTransformations: How data is modifiedexternalDependencies: External services, APIs, databases accessedconfigurationDependencies: Config values, feature flags, settingsconditionalLogic: Key decision points and brancheserrorScenarios: What can go wrong, error handlingFor Consumers/Message Bus:
messageBusMessage: Message type consumedmessageBusProducers: Who sends this message (grep across all services)crossServiceIntegration: Cross-service data flowMANDATORY: After every 10 files, update Items Processed and run CONTEXT_ANCHOR_CHECK.
Under ## Data Flow, document:
Create a text-based flow diagram:
[Entry] → [Step 1] → [Step 2] → [Step 3] → [Exit]
↓ ↓
[Side Effect] [Database]
Document under ## Workflow Analysis:
Document under ## Architectural Analysis:
Document under ## Business Logic:
Write a clear, concise answer to the original question under ## Executive Summary:
Under ## Detailed Explanation:
Under ## Diagrams:
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Component │────>│ Command │────>│ Handler │
└─────────────┘ └─────────────┘ └─────────────┘
│
v
┌─────────────┐
│ Repository │
└─────────────┘
Under ## Related Discoveries:
Present your findings to the user in a clear, organized format:
## Answer
[Direct answer to the question in 1-2 paragraphs]
## How It Works
### 1. [First Step]
[Explanation with code reference at `file:line`]
### 2. [Second Step]
[Explanation with code reference at `file:line`]
...
## Key Files
| File | Purpose |
| --------------------- | --------- |
| `path/to/file.cs:123` | [Purpose] |
## Data Flow
[Text diagram showing the flow]
## Want to Know More?
I can explain further:
- [Topic 1]
- [Topic 2]
- [Topic 3]
PlatformCqrsCommand / PlatformCqrsQuery - CQRS entry pointsPlatformCqrsEntityEventApplicationHandler - Side effectsPlatformApplicationMessageBusConsumer - Cross-service consumersIPlatformQueryableRootRepository / IPlatformQueryableRootRepository - Data accessPlatformValidationResult - Validation logic[PlatformAuthorize] - AuthorizationAppBaseVmStoreComponent - State management componentsPlatformVmStore - Store implementationseffectSimple / tapResponse - Effect handlingobserverLoadingErrorState - Loading/error statesPlatformApiServicefeature-implementation skill - For implementing new features (code changes)bug-diagnosis skill - For debugging and fixing issuestasks-feature-implementation skill - Autonomous feature implementation variant.ai/prompts/context.md - Platform patterns and contextCLAUDE.md - Codebase instructionsxiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience