- Default to Server Components in
app/, only using Client Components with'use client'if they use hooks likeuseStateoruseRouter, or DOM interactions. - Fetching data in Server Components: use
fetch(), avoiduseEffect. - For TypeScript: Enforce interfaces and types for all props and state.
- Nest
layout.tsxfiles for consistent UI across sections. - For async operations: prefer
async/await, add appropriate error handling and UI loading states.
- GitHub Staff
- http://digitarald.de
- @digitarald
| { | |
| "github.copilot.chat.experimental.codeGeneration.useInstructionFiles": true, | |
| "github.copilot.chat.experimental.codeGeneration.instructions": [ | |
| { | |
| "text": "Use concise one-liners when possible, but avoid sacrificing clarity for brevity." | |
| }, | |
| { | |
| "text": "Comment any generated code that has complex logic, especially around asynchronous operations or state management." | |
| }, | |
| { |
The software development landscape is experiencing a fundamental transformation. Recent research social/blogs content from early AI adopters reveals three distinct AI-assisted methodologies that are redefining how code is created, each serving different developer needs while delivering what practitioners describe as "exponential productivity gains."
Developers tackling complex projects with significant architectural requirements are finding success with highly structured AI workflows that emphasize thorough planning before implementation:
| { | |
| "inputs": [ | |
| { | |
| "type": "promptString", | |
| "id": "github-pat", | |
| "password": true, | |
| "description": "GitHub Personal Access Token (PAT, https://github.com/settings/personal-access-tokens/new)" | |
| } | |
| ], | |
| "servers": { |
| description | Research and draft an implementation plan | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| tools |
|
You are pairing with the user to create a clear, detailed, and actionable plan for the given task, iterating through a of gathering context and drafting the plan for review.
Comprehensive context gathering for planning following : 1. Context gathering and research: - MANDATORY: MUST run `execute_prompt` tool: Instruct the agent to work autonomously without pausing for user feedback, following to gather context to return to you.| name | GitHub Research | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| description | GitHub graph search expert. Use to answer complex questions that require exploring GitHub repos, issues, PRs, commits, etc. Run MULTIPLE in parallel to explore different repos or search angles. | |||||||||||||||||||
| tools |
|
|||||||||||||||||||
| agents |
|
|||||||||||||||||||
| model |
|
You are a GitHub graph search expert. Given a query, explore GitHub's repositories, issues, PRs, commits, and code to gather relevant information.
FIRST, check if you have access to #tool:agent/runSubagent with the 'GitHub Res