Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-22 11:25:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert "fetch -> web/fetch for everything"

Browse Source 
This reverts commit ca790b1716.
This commit is contained in:
Jon Corbin
2026-01-12 14:03:48 -05:00
parent e8577617b0
commit 5afc90e633
69 changed files with 360 additions and 360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

120
prompts/folder-structure-blueprint-generator.prompt.md
View File

@@ -7,34 +7,34 @@ agent: 'agent'
## Configuration Variables
${PROJECT_TYPE="Auto-detect|.NET|Java|React|Angular|Python|Node.js|Flutter|Other"}
${PROJECT_TYPE="Auto-detect|.NET|Java|React|Angular|Python|Node.js|Flutter|Other"}
<!-- Select primary technology -->
${INCLUDES_MICROSERVICES="Auto-detect|true|false"}
${INCLUDES_MICROSERVICES="Auto-detect|true|false"}
<!-- Is this a microservices architecture? -->
${INCLUDES_FRONTEND="Auto-detect|true|false"}
${INCLUDES_FRONTEND="Auto-detect|true|false"}
<!-- Does project include frontend components? -->
${IS_MONOREPO="Auto-detect|true|false"}
${IS_MONOREPO="Auto-detect|true|false"}
<!-- Is this a monorepo with multiple projects? -->
${VISUALIZATION_STYLE="ASCII|Markdown List|Table"}
${VISUALIZATION_STYLE="ASCII|Markdown List|Table"}
<!-- How to visualize the structure -->
${DEPTH_LEVEL=1-5}
${DEPTH_LEVEL=1-5}
<!-- How many levels of folders to document in detail -->
${INCLUDE_FILE_COUNTS=true|false}
${INCLUDE_FILE_COUNTS=true|false}
<!-- Include file count statistics -->
${INCLUDE_GENERATED_FOLDERS=true|false}
${INCLUDE_GENERATED_FOLDERS=true|false}
<!-- Include auto-generated folders -->
${INCLUDE_FILE_PATTERNS=true|false}
${INCLUDE_FILE_PATTERNS=true|false}
<!-- Document file naming/location patterns -->
${INCLUDE_TEMPLATES=true|false}
${INCLUDE_TEMPLATES=true|false}
<!-- Include file/folder templates for new features -->
## Generated Prompt
@@ -43,7 +43,7 @@ ${INCLUDE_TEMPLATES=true|false}
### Initial Auto-detection Phase
${PROJECT_TYPE == "Auto-detect" ?
${PROJECT_TYPE == "Auto-detect" ?
"Begin by scanning the folder structure for key files that identify the project type:
- Look for solution/project files (.sln, .csproj, .fsproj, .vbproj) to identify .NET projects
- Check for build files (pom.xml, build.gradle, settings.gradle) for Java projects
@@ -51,17 +51,17 @@ ${PROJECT_TYPE == "Auto-detect" ?
- Look for specific framework files (angular.json, react-scripts entries, next.config.js)
- Check for Python project identifiers (requirements.txt, setup.py, pyproject.toml)
- Examine mobile app identifiers (pubspec.yaml, android/ios folders)
- Note all technology signatures found and their versions" :
- Note all technology signatures found and their versions" :
"Focus analysis on ${PROJECT_TYPE} project structure"}
${IS_MONOREPO == "Auto-detect" ?
${IS_MONOREPO == "Auto-detect" ?
"Determine if this is a monorepo by looking for:
- Multiple distinct projects with their own configuration files
- Workspace configuration files (lerna.json, nx.json, turborepo.json, etc.)
- Cross-project references and shared dependency patterns
- Root-level orchestration scripts and configuration" : ""}
${INCLUDES_MICROSERVICES == "Auto-detect" ?
${INCLUDES_MICROSERVICES == "Auto-detect" ?
"Check for microservices architecture indicators:
- Multiple service directories with similar/repeated structures
- Service-specific Dockerfiles or deployment configurations
@@ -70,7 +70,7 @@ ${INCLUDES_MICROSERVICES == "Auto-detect" ?
- API gateway configuration files
- Shared libraries or utilities across services" : ""}
${INCLUDES_FRONTEND == "Auto-detect" ?
${INCLUDES_FRONTEND == "Auto-detect" ?
"Identify frontend components by looking for:
- Web asset directories (wwwroot, public, dist, static)
- UI framework files (components, modules, pages)
@@ -87,40 +87,40 @@ Provide a high-level overview of the ${PROJECT_TYPE == "Auto-detect" ? "detected
- Note any structural patterns that repeat throughout the codebase
- Document the rationale behind the structure where it can be inferred
${IS_MONOREPO == "Auto-detect" ?
"If detected as a monorepo, explain how the monorepo is organized and the relationship between projects." :
${IS_MONOREPO == "Auto-detect" ?
"If detected as a monorepo, explain how the monorepo is organized and the relationship between projects." :
IS_MONOREPO ? "Explain how the monorepo is organized and the relationship between projects." : ""}
${INCLUDES_MICROSERVICES == "Auto-detect" ?
"If microservices are detected, describe how they are structured and organized." :
${INCLUDES_MICROSERVICES == "Auto-detect" ?
"If microservices are detected, describe how they are structured and organized." :
INCLUDES_MICROSERVICES ? "Describe how the microservices are structured and organized." : ""}
### 2. Directory Visualization
${VISUALIZATION_STYLE == "ASCII" ?
${VISUALIZATION_STYLE == "ASCII" ?
"Create an ASCII tree representation of the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
${VISUALIZATION_STYLE == "Markdown List" ?
${VISUALIZATION_STYLE == "Markdown List" ?
"Use nested markdown lists to represent the folder hierarchy to depth level ${DEPTH_LEVEL}." : ""}
${VISUALIZATION_STYLE == "Table" ?
${VISUALIZATION_STYLE == "Table" ?
"Create a table with columns for Path, Purpose, Content Types, and Conventions." : ""}
${INCLUDE_GENERATED_FOLDERS ?
"Include all folders including generated ones." :
${INCLUDE_GENERATED_FOLDERS ?
"Include all folders including generated ones." :
"Exclude auto-generated folders like bin/, obj/, node_modules/, etc."}
### 3. Key Directory Analysis
Document each significant directory's purpose, contents, and patterns:
${PROJECT_TYPE == "Auto-detect" ?
${PROJECT_TYPE == "Auto-detect" ?
"For each detected technology, analyze directory structures based on observed usage patterns:" : ""}
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
"#### .NET Project Structure (if detected)
- **Solution Organization**:
- **Solution Organization**:
- How projects are grouped and related
- Solution folder organization patterns
- Multi-targeting project patterns
@@ -149,7 +149,7 @@ ${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
- Test categories and organization
- Test data and mock locations" : ""}
${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ?
${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ?
"#### UI Project Structure (if detected)
- **Component Organization**:
@@ -170,13 +170,13 @@ ${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto
- **API Integration**:
- API client organization
- Service layer structure
- Data web/fetching patterns
- Data fetching patterns
- **Asset Management**:
- Static resource organization
- Image/media file structure
- Font and icon organization
- **Style Organization**:
- CSS/SCSS file structure
- Theme organization
@@ -184,36 +184,36 @@ ${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto
### 4. File Placement Patterns
${INCLUDE_FILE_PATTERNS ?
${INCLUDE_FILE_PATTERNS ?
"Document the patterns that determine where different types of files should be placed:
- **Configuration Files**:
- Locations for different types of configuration
- Environment-specific configuration patterns
- **Model/Entity Definitions**:
- Where domain models are defined
- Data transfer object (DTO) locations
- Schema definition locations
- **Business Logic**:
- Service implementation locations
- Business rule organization
- Utility and helper function placement
- **Interface Definitions**:
- Where interfaces and abstractions are defined
- How interfaces are grouped and organized
- **Test Files**:
- Unit test location patterns
- Integration test placement
- Test utility and mock locations
- **Documentation Files**:
- API documentation placement
- Internal documentation organization
- README file distribution" :
- README file distribution" :
"Document where key file types are located in the project."}
### 5. Naming and Organization Conventions
@@ -223,12 +223,12 @@ Document the naming and organizational conventions observed across the project:
- Case conventions (PascalCase, camelCase, kebab-case)
- Prefix and suffix patterns
- Type indicators in filenames
- **Folder Naming Patterns**:
- Naming conventions for different folder types
- Hierarchical naming patterns
- Grouping and categorization conventions
- **Namespace/Module Patterns**:
- How namespaces/modules map to folder structure
- Import/using statement organization
@@ -252,13 +252,13 @@ Provide guidance for navigating and working with the codebase structure:
- How to extend existing functionality
- Where to place new tests
- Configuration modification locations
- **Dependency Patterns**:
- How dependencies flow between folders
- Import/reference patterns
- Dependency injection registration locations
${INCLUDE_FILE_COUNTS ?
${INCLUDE_FILE_COUNTS ?
"- **Content Statistics**:
- Files per directory analysis
- Code distribution metrics
@@ -271,12 +271,12 @@ Document the build process and output organization:
- Build script locations and purposes
- Build pipeline organization
- Build task definitions
- **Output Structure**:
- Compiled/built output locations
- Output organization patterns
- Distribution package structure
- **Environment-Specific Builds**:
- Development vs. production differences
- Environment configuration strategies
@@ -284,7 +284,7 @@ Document the build process and output organization:
### 8. Technology-Specific Organization
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
"#### .NET-Specific Structure Patterns (if detected)
- **Project File Organization**:
@@ -292,53 +292,53 @@ ${(PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect") ?
- Target framework configuration
- Property group organization
- Item group patterns
- **Assembly Organization**:
- Assembly naming patterns
- Multi-assembly architecture
- Assembly reference patterns
- **Resource Organization**:
- Embedded resource patterns
- Localization file structure
- Static web asset organization
- **Package Management**:
- NuGet configuration locations
- Package reference organization
- Package version management" : ""}
${(PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect") ?
${(PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect") ?
"#### Java-Specific Structure Patterns (if detected)
- **Package Hierarchy**:
- Package naming and nesting conventions
- Domain vs. technical packages
- Visibility and access patterns
- **Build Tool Organization**:
- Maven/Gradle structure patterns
- Module organization
- Plugin configuration patterns
- **Resource Organization**:
- Resource folder structures
- Environment-specific resources
- Properties file organization" : ""}
${(PROJECT_TYPE == "Node.js" || PROJECT_TYPE == "Auto-detect") ?
${(PROJECT_TYPE == "Node.js" || PROJECT_TYPE == "Auto-detect") ?
"#### Node.js-Specific Structure Patterns (if detected)
- **Module Organization**:
- CommonJS vs. ESM organization
- Internal module patterns
- Third-party dependency management
- **Script Organization**:
- npm/yarn script definition patterns
- Utility script locations
- Development tool scripts
- **Configuration Management**:
- Configuration file locations
- Environment variable management
@@ -351,18 +351,18 @@ Document how the project structure is designed to be extended:
- How to add new modules/features while maintaining conventions
- Plugin/extension folder patterns
- Customization directory structures
- **Scalability Patterns**:
- How the structure scales for larger features
- Approach for breaking down large modules
- Code splitting strategies
- **Refactoring Patterns**:
- Common refactoring approaches observed
- How structural changes are managed
- Incremental reorganization patterns
${INCLUDE_TEMPLATES ?
${INCLUDE_TEMPLATES ?
"### 10. Structure Templates
Provide templates for creating new components that follow project conventions:
@@ -371,17 +371,17 @@ Provide templates for creating new components that follow project conventions:
- Folder structure for adding a complete feature
- Required file types and their locations
- Naming patterns to follow
- **New Component Template**:
- Directory structure for a typical component
- Essential files to include
- Integration points with existing structure
- **New Service Template**:
- Structure for adding a new service
- Interface and implementation placement
- Configuration and registration patterns
- **New Test Structure**:
- Folder structure for test projects/files
- Test file organization templates
@@ -395,7 +395,7 @@ Document how the project structure is maintained and enforced:
- Tools/scripts that enforce structure
- Build checks for structural compliance
- Linting rules related to structure
- **Documentation Practices**:
- How structural changes are documented
- Where architectural decisions are recorded