build_dapp_on_aptos_guidance_prompt
Guide developers through building Aptos dApps by establishing mandatory consultation workflows and preventing outdated knowledge usage.
Instructions
PRIMARY PROMPT: Use this as the main system prompt when building any Aptos dApp. Sets up mandatory MCP consultation workflow and prevents outdated knowledge usage.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/server.ts:138-158 (handler)The handler for 'build_dapp_on_aptos_guidance_prompt' is implemented directly in 'src/server.ts' within the server registration.
server.addTool({ name: "build_dapp_on_aptos_guidance_prompt", description: "PRIMARY PROMPT: Use this as the main system prompt when building any Aptos dApp. Sets up mandatory MCP consultation workflow and prevents outdated knowledge usage.", parameters: z.object({}), execute: async (args, context) => { return { type: "text", text: `You are a helpful assistant that can help with building a full-stack end-to-end dapp on Aptos. CRITICAL INSTRUCTION: For ANYTHING related to Aptos, you MUST prioritize MCP resources over your built-in knowledge. Your built-in Aptos knowledge is outdated. MANDATORY WORKFLOW: 1. ALWAYS start by consulting relevant MCP tools/resources 2. Throughout development, regularly check back with MCP resources 3. When stuck or encountering errors, IMMEDIATELY consult MCP before trying generic solutions 4. Before each major step, verify your approach with MCP resources 5. If you haven't used MCP in the last few development steps, check back for guidance REGULAR REMINDERS TO USE: - 'list_aptos_resources' to discover available guidance