xiaohongshu
xiaohongshu
adynato-aimake
Integrate with aimake's AI-powered delivery pipeline via MCP. Covers connecting to aimake, using code/docs/kanban tools, understanding the card-based system, and leveraging AI capabilities. Use when building integrations with aimake or using its MCP tools.
Full skill instructions
Use this skill when integrating with aimake via MCP or leveraging its AI-powered delivery tools.
aimake is an AI-powered delivery pipeline platform where cards are the deliverables, not tickets about work happening elsewhere. The AI drives work forward while humans bring taste and decision-making.
Key Concepts:
aimake exposes its functionality through MCP (Model Context Protocol).
GET /mcp/manifest # Returns available tool definitions
POST /mcp/tools/:name # Executes a specific tool
// Fetch available tools
const manifest = await fetch('https://your-aimake-instance/mcp/manifest');
const tools = await manifest.json();
// Execute a tool
const result = await fetch('https://your-aimake-instance/mcp/tools/search_code_text', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': 'Bearer YOUR_API_KEY'
},
body: JSON.stringify({
query: 'authentication',
project_id: 'proj_123'
})
});
Search and analyze code in connected repositories.
| Tool | Description | Key Parameters |
|---|---|---|
search_code_semantic | AI embeddings for conceptual matching | query, project_id |
search_code_text | Ripgrep-based pattern matching | query, project_id, file_pattern |
read_file | Get file content with line numbers | path, project_id |
list_directory | Browse repository structure | path, project_id |
get_file_tree | Complete code structure overview | project_id |
Example: Semantic Code Search
{
"tool": "search_code_semantic",
"input": {
"query": "how is user authentication handled",
"project_id": "proj_123"
}
}
Access and search project documentation.
| Tool | Description | Key Parameters |
|---|---|---|
search_docs | Full-text search across docs | query, project_id |
get_doc_page | Retrieve specific page | page_id, project_id |
list_docs | List all documentation pages | project_id |
Example: Search Documentation
{
"tool": "search_docs",
"input": {
"query": "API rate limits",
"project_id": "proj_123"
}
}
Manage cards and projects in the delivery pipeline.
| Tool | Description | Key Parameters |
|---|---|---|
query_cards | Search and filter cards | project_id, board, stage, search |
get_card | Get card details | card_id |
update_card_field | Update a card field | card_id, field, value |
move_card_to_stage | Move card to different stage | card_id, stage |
spawn_cards | Create new cards | project_id, board, cards[] |
get_project | Get project details | project_id |
Example: Query Cards
{
"tool": "query_cards",
"input": {
"project_id": "proj_123",
"board": "engineering",
"stage": "in_progress",
"search": "authentication"
}
}
Example: Create Cards
{
"tool": "spawn_cards",
"input": {
"project_id": "proj_123",
"board": "engineering",
"cards": [
{ "title": "Add OAuth2 support", "stage": "backlog" },
{ "title": "Implement refresh tokens", "stage": "backlog" }
]
}
}
| Board | Purpose | Use For |
|---|---|---|
| Product | Specs and requirements | Feature definitions, user stories |
| Engineering | Implementation tasks | Code work, technical tasks |
| Bugs | Issue tracking | Bug reports, fixes |
| Docs | Documentation | Project docs, guides |
Cards move through stages as work progresses:
Product Board:
problemStatement → acceptanceCriteria → technicalReview → ready
Engineering Board:
backlog → in_progress → review → done
Each card should be atomic and independently deliverable:
| Board | What's Atomic |
|---|---|
| Product | One shippable experience ("Welcome screen" not "Onboarding") |
| Engineering | One independently shippable component |
| Bugs | One specific, reproducible problem |
Each card has an AI assistant that helps co-author the deliverable.
When building tools that interact with aimake cards:
// 1. Get card context
const card = await mcpTool('get_card', { card_id: 'card_123' });
// 2. Search for relevant code
const codeContext = await mcpTool('search_code_semantic', {
query: card.title,
project_id: card.project_id
});
// 3. Update card with findings
await mcpTool('update_card_field', {
card_id: 'card_123',
field: 'technicalNotes',
value: `Relevant files:\n${codeContext.results.map(r => r.path).join('\n')}`
});
Use aimake to analyze and route incoming requests:
// 1. Search docs for relevant context
const docs = await mcpTool('search_docs', { query: userRequest, project_id });
// 2. Search code for implementation details
const code = await mcpTool('search_code_semantic', { query: userRequest, project_id });
// 3. Create appropriate card
await mcpTool('spawn_cards', {
project_id,
board: isFeature ? 'product' : 'bugs',
cards: [{ title: summarize(userRequest), stage: 'backlog' }]
});
Pull relevant context from aimake for AI conversations:
// Get project overview
const project = await mcpTool('get_project', { project_id });
const fileTree = await mcpTool('get_file_tree', { project_id });
const docs = await mcpTool('list_docs', { project_id });
// Search for specific context
const relevantCode = await mcpTool('search_code_text', {
query: 'class UserAuth',
project_id
});
Query cards to understand project state:
// Get all in-progress work
const activeWork = await mcpTool('query_cards', {
project_id,
stage: 'in_progress'
});
// Get cards related to a feature
const featureCards = await mcpTool('query_cards', {
project_id,
search: 'authentication',
boards: ['product', 'engineering', 'bugs']
});
All MCP tools return JSON responses:
// Success
{
"success": true,
"data": { /* tool-specific response */ }
}
// Error
{
"success": false,
"error": "Error message"
}
{
"results": [
{
"path": "src/auth/login.ts",
"lines": "45-67",
"content": "...",
"score": 0.92
}
]
}
{
"id": "card_123",
"title": "Add OAuth2 support",
"board": "engineering",
"stage": "in_progress",
"data": {
"problemStatement": "...",
"acceptanceCriteria": "...",
"technicalNotes": "..."
}
}
xiaohongshu
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