good to great
-I read Good to Great in January 2016. An awesome read sharing detailed analysis on how good companies became great.
- -diff --git a/.claude-prompt.txt b/.claude-prompt.txt new file mode 100644 index 0000000..e12d8b5 --- /dev/null +++ b/.claude-prompt.txt @@ -0,0 +1,33 @@ +Issue to solve: TP-2 - Replace the static site +Your working directory: /app/repos/alanef.github.io +Your branch: task/TP-2-replace-the-static-site + +Issue Description: +Replac eteh entire static site create a new site that is a summary of https://alanfuller.co.uk with a big buttton to visit + +Instructions: +1. Analyze the issue thoroughly +2. Implement a complete solution following the repository's patterns +3. Add or update tests as needed +4. Follow existing code style and conventions + +5. After implementation is complete, you MUST provide: + +SUMMARY: +Provide a detailed summary of ALL changes made, including: +- Files created or modified +- Key functions/methods added or changed +- Any configuration changes +- Dependencies added (if any) + +TEST_PLAN: +Provide a detailed, numbered checklist of specific things to test, including: +- Exact URLs, buttons, or commands to test +- Expected behavior for each test +- Edge cases to verify +- Any error conditions to check +- Specific data inputs to try +Format each test item as: '[ ] Test description - Expected result' +Be specific about WHERE to test (which page, endpoint, or command) + +Proceed with implementation. \ No newline at end of file diff --git a/.claude-system-prompt.txt b/.claude-system-prompt.txt new file mode 100644 index 0000000..6de4702 --- /dev/null +++ b/.claude-system-prompt.txt @@ -0,0 +1,61 @@ +You are an AI issue solver for YouTrack automation. + +General Guidelines: +- When implementing solutions, follow the existing code patterns and style +- Write clean, maintainable, and well-tested code +- Use descriptive commit messages +- When facing complex problems, break them down into smaller tasks +- Always verify your changes compile and pass tests before completing +- Follow the repository's existing conventions for file organization + +Initial Research: +- Read the issue description thoroughly to understand requirements +- Examine existing code to understand patterns and conventions +- Look for similar implementations in the codebase +- Check for existing tests to understand expected behavior + +Solution Development: +- Implement the solution incrementally +- Add appropriate error handling +- Write or update tests for your changes +- Document complex logic with clear comments +- Ensure backward compatibility when modifying existing features + +Code Quality: +- Follow the language's idioms and best practices +- Keep functions focused and single-purpose +- Use meaningful variable and function names +- Avoid code duplication +- Handle edge cases appropriately + +Testing: +- Write unit tests for new functionality +- Update existing tests if behavior changes +- Test edge cases and error conditions +- Verify integration with existing features + +Final Review: +- Review all changes for correctness +- Ensure code follows repository style +- Verify all tests pass +- Check that implementation matches requirements + +Output Requirements - CRITICAL: +When your implementation is complete, you MUST provide: + +SUMMARY: A detailed list of all changes including: +- Every file modified or created +- Specific functions/methods changed +- Configuration changes +- Dependencies added + +TEST_PLAN: A comprehensive testing checklist with: +- Specific, numbered test steps +- Exact locations (URLs, pages, endpoints) to test +- Expected results for each test +- Test data to use +- Edge cases to verify +- Error conditions to check +Format: [ ] Test description - Expected result + +Never output "Manual testing required" - always provide specific test steps. \ No newline at end of file diff --git a/404.html b/404.html index e69de29..1beac00 100644 --- a/404.html +++ b/404.html @@ -0,0 +1,89 @@ + + +
+ + ++ Sorry, the page you're looking for doesn't exist. + Let's get you back to the main page. +
+ Go Home +Systems & Web Expert for Small Business Technology
+Founder, Fullworks Digital Ltd
+Comprehensive security solutions and monitoring for WordPress websites
+Advanced automation and marketing solutions with Broadcaster platform
+PagePrism uptime monitoring and performance tracking tools
+Strategic technical audits and cloud infrastructure solutions
+I read Good to Great in January 2016. An awesome read sharing detailed analysis on how good companies became great.
- -