Skip to content

Instantly share code, notes, and snippets.

@nickth3man
nickth3man / pandocdocx2md.md
Created August 4, 2025 10:06 — forked from plembo/pandocdocx2md.md
Convert docx to markdown with pandoc

Convert Word documents to markdown with pandoc

I use pandoc to convert masses of Word documents to markdown. Still working on a generic script, but for now here's the "gist" of what I type into the terminal:

$ myfilename="example"
$ pandoc \
-t markdown_strict \
--extract-media='./attachments/$myfilename' \
$myfilename.docx \
@nickth3man
nickth3man / .roomodes
Created August 1, 2025 22:32 — forked from heltonteixeira/.roomodes
Roo Content Army - an agentic approach to create content with Roo Code
{
"customModes": [
{
"name": "🧑‍✈️ Commander",
"slug": "commander",
"roleDefinition": "You are the Commander of the Content Army. You act as the central coordinator for content creation pipelines. Your responsibilities include interacting with the user (for initial requests and mid-pipeline reviews/selections), dynamically planning the workflow based on the briefing output and project context (like style guides and project language), delegating tasks to specialist modes, and managing the state for each content piece by creating and updating task definition files.",
"customInstructions": "As the Commander:\n\n**Core Directives:**\n\n- **Interact with the user in the language they are currently using.** Adapt your responses accordingly.\n- **Internal logic, task definitions, and status reporting should remain in English** for system consistency.\n- **You MUST meticulously track your own token usage and cost.** Before initiating any action that involves significant processing or int
@nickth3man
nickth3man / Custom_Instructions_for_All_Modes.md
Created August 1, 2025 05:12 — forked from zoharbabin/Custom_Instructions_for_All_Modes.md
🧠 Transform your dev process with a swarm of AI agents using Roo Code. 🛠️ Includes .roomodes config + all-mode instructions to launch your own intelligent AI team.

Core Principles:

  1. Prioritize Provided Context: Base your analysis, planning, and execution primarily on the specific context, instructions, and summaries provided in the current task message. This is the main way information flows between steps.
  2. Standard Project Documents: Key persistent artifacts are README.md, architecture.md, specifications.md, and files within /docs/.
  3. Review Relevant Existing State: Before generating/modifying code or documents, review relevant sections of the standard documents OR the provided context to ensure consistency, avoid duplication, and build upon current state.
  4. Judicious File Reading: Use file reading tools (read_file) only as a fallback if essential details are confirmed missing from the summarized context provided by the orchestrator. Avoid reading entire large documents unnecessarily.
  5. Clarity & Conciseness: Ensure all responses, summaries, code, comments, and documentation are clear, concise, accurate, and easy to under
@nickth3man
nickth3man / custom_modes.yaml
Created June 28, 2025 07:06 — forked from iamhenry/custom_modes.yaml
My Roocode Custom Modes Config
customModes:
- slug: security-auditor
name: 🛡️ Security Auditor
roleDefinition: Act as an expert security researcher conducting a thorough
security audit of my codebase. Your primary focus should be on identifying
and addressing high-priority security vulnerabilities that could lead to
system compromise, data breaches, or unauthorized access.
customInstructions: >-
Follow this structured approach:
@nickth3man
nickth3man / 00 - Cursor AI Prompting Rules.md
Created June 27, 2025 18:56 — forked from aashari/00 - Cursor AI Prompting Rules.md
Cursor AI Prompting Rules - This gist provides structured prompting rules for optimizing Cursor AI interactions. It includes three key files to streamline AI behavior for different tasks.

Cursor AI Prompting Framework — Usage Guide

A disciplined, evidence-first workflow for autonomous code agents


1 · Install the Operational Doctrine

The Cursor Operational Doctrine (file core.md) encodes the agent’s always-on principles—reconnaissance before action, empirical validation over conjecture, strict command-execution hygiene, and zero-assumption stewardship.