| #!/bin/bash | |
| # What Is This | |
| # A way to compare downloads in folder A to hardlinks in folder B. Useful to see if your | |
| # "use hardlinks" logic in the ARRS is working | |
| # | |
| # Separation of Concerns (AI yackin') | |
| # The logic for calculating the 2TB physical limit is isolated from the descriptive logic | |
| # used for the detailed file list. | |
| # |
| description | Use when the user asks to "call a quorum" or "assemble a quorum" | |
|---|---|---|
| argument-hint |
|
Derive TOPIC from $ARGUMENTS and conversation context.
| I want you to refine this brainstorming document into a prompt for a deep research system that will be tasked with writing a technical spike | |
| research document on a software engineering project. The goal of this research is to help guide future agentic coding systems into | |
| having a good understanding of the technical landscape around the software the user wants to create. | |
| <context> | |
| Deep research is a category of product where large language models capable of test time compute are paired with capacities to: | |
| - search the web | |
| - browse documentatin | |
| - read research paper | |
| - further refine their research based on their finding |
| Security Measure | Description | |
|---|---|---|
| ☐ | Use HTTPS everywhere | Prevents basic eavesdropping and man-in-the-middle attacks |
| ☐ | Input validation and sanitization | Prevents XSS attacks by validating all user inputs |
| ☐ | Don't store sensitive data in the browser | No secrets in localStorage or client-side code |
| ☐ | CSRF protection | Implement anti-CSRF tokens for forms and state-changing requests |
| ☐ | Never expose API keys in frontend | API credentials should always remain server-side |
| I want you to refine this brainstorming document into a prompt for a deep research system that will be tasked with writing a technical spike | |
| research document on a software engineering project. The goal of this research is to help guide future agentic coding systems into | |
| having a good understanding of the technical landscape around the software the user wants to create. | |
| <context> | |
| Deep research is a category of product where large language models capable of test time compute are paired with capacities to: | |
| - search the web | |
| - browse documentatin | |
| - read research paper | |
| - further refine their research based on their finding |
This repository contains a disciplined, evidence-first prompting framework designed to elevate an Agentic AI from a simple command executor to an Autonomous Principal Engineer.
The philosophy is simple: Autonomy through discipline. Trust through verification.
This framework is not just a collection of prompts; it is a complete operational system for managing AI agents. It enforces a rigorous workflow of reconnaissance, planning, safe execution, and self-improvement, ensuring every action the agent takes is deliberate, verifiable, and aligned with senior engineering best practices.
I also have Claude Code prompting for your reference: https://gist.github.com/aashari/1c38e8c7766b5ba81c3a0d4d124a2f58
| #!/bin/bash | |
| # Default values | |
| verbose=0 | |
| min_battery=20 | |
| log() { | |
| if [[ "$verbose" -gt 0 ]]; then | |
| echo "$@" | |
| fi |
| #!/bin/bash | |
| ###### Tasks Requiring Manual Checking ###### | |
| # Review Installed Applications: | |
| # Steps: Open Applications folder and Launchpad. | |
| # Signs of Compromise: Unfamiliar or unexpected applications installed. | |
| # Check App Permissions: | |
| # Steps: System Preferences → Security & Privacy → Privacy tab. | |
| # Signs of Compromise: Unusual permissions granted to unknown applications. | |
| # Audit Browser Extensions: |
| #!/bin/zsh | |
| # Ensure Xcode and Command Line Tools are installed | |
| xcode-select --install | |
| sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer | |
| sudo xcodebuild -license | |
| # Install Homebrew | |
| which -s brew |
