https://github.com/powerappsdarren/power-fx-coding
Power-Fx-Coding
https://github.com/powerappsdarren/power-fx-coding
Last synced: about 1 year ago
JSON representation
Power-Fx-Coding
- Host: GitHub
- URL: https://github.com/powerappsdarren/power-fx-coding
- Owner: PowerAppsDarren
- Created: 2025-04-07T16:35:21.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-05-06T23:21:24.000Z (about 1 year ago)
- Last Synced: 2025-05-07T00:27:38.075Z (about 1 year ago)
- Language: Shell
- Size: 375 KB
- Stars: 3
- Watchers: 1
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Project Template
➡️ This repository is set up as a template for starting new projects with consistent structure and documentation.
Hey there, developer! 👋 Welcome to your new project! 🚀
>You will want to start [here](/+Developers-Start-Here/README.md) after reviewing this read-me file you're reading now!
>This template is designed to help you get started with a new project by providing a consistent structure and documentation system.
## Getting Started
1. Replace project-specific details in this README
2. Review and modify the folder structure as needed
3. Update any template files to match your project requirements
4. Follow the documentation guidelines for all future conversations and code changes
# Listen up, AI! This is Important!
The rest of this readme file is for you, AI!
>**IMPORTANT:** This project is set up to ensure that all conversations with GitHub Copilot are documented in a specific format. This is crucial for maintaining a clear record of the development process and decisions made throughout the project lifecycle.
## 🤖 To Start Things Off Right...
When you open a new Copilot chat session, be sure to paste this message to ensure we follow the documentation structure correctly:
```
Please reference the README.md documentation requirements for our conversation structure.
#file:README.md ⬅️ Remember: Each exchange needs its own numbered markdown file in the appropriate dated folder under Copilot-Chats. #codebase
```
## Documentation
This repository includes a `Copilot-Chats` folder containing documentation of all GitHub Copilot conversations related to this project.
### Chat Documentation Structure
For all GitHub Copilot conversations related to this project, we maintain the following documentation structure:
1. **Folder Organization**:
- Main folder: `Copilot-Chats/`
- Conversation folders: `yyyy-mm-dd-brief-description/` (e.g., `2023-10-25-folder-structure-setup/`)
2. **File Naming**:
- Files within each conversation folder are numbered sequentially
- Format: `##-brief-description.md` (e.g., `01-initial-setup.md`, `02-confirmation.md`)
3. **File Content**:
- Each file contains both the prompt and the response
- Structured with headings for clarity (## Prompt, ## Response)
### ⚠️ IMPORTANT - DOCUMENTATION COMPLIANCE ⚠️
**It is CRITICALLY IMPORTANT that this documentation structure is followed WITHOUT EXCEPTION for EVERY interaction related to this project.**
- EVERY conversation must be documented
- EVERY exchange must have its own numbered file
- NO exchanges should be skipped or merged
- Sequential numbering must be maintained
This strict documentation system is essential for maintaining a complete record of the development process, decisions made, and solutions provided throughout the project lifecycle.
When starting a new conversation about this project, reference this README to maintain consistent documentation.
---
>
>🚀 **Ready to get started?**
>
>➡️➡️ You will want to go [here next / now](/+Developers-Start-Here/README.md) now that you have reviewed this file! ⬅️⬅️
>