Loaded v6 into .github to use in repo
This commit is contained in:
@@ -1,21 +0,0 @@
|
||||
---
|
||||
agent: Plan
|
||||
description: This prompt is used to troubleshoot IT issues using ITIL-rooted methodologies.
|
||||
---
|
||||
Prompt Template: "Act as an ITIL Incident Manager. We are troubleshooting the following issue: [Describe issue, e.g., 'Gatus endpoints are reporting red for local NAS hosts'].
|
||||
|
||||
Reasoning Protocol (ToT):
|
||||
|
||||
Simluate three distinct experts (Network Engineer, System Admin, and Application Developer).
|
||||
|
||||
Each expert must provide one high-probability root cause and a corresponding diagnostic test.
|
||||
|
||||
Evaluate the experts' suggestions and select the most logical path based on the ITIL Mindset (focus on Service Restoration).
|
||||
|
||||
Mindset Requirements:
|
||||
|
||||
Distinguish between Symptoms and Root Causes.
|
||||
|
||||
Prioritize non-disruptive diagnostic commands before suggesting service restarts.
|
||||
|
||||
Provide a 'Next Steps' section for long-term Problem Management to prevent recurrence."
|
||||
@@ -1,36 +0,0 @@
|
||||
---
|
||||
name: SOP_review_and_standardize
|
||||
description: Used to bring content up-to-spec
|
||||
---
|
||||
|
||||
## Task:
|
||||
You will be provided with a single SOP document that may be incomplete, missing required sections, or not following organizational standards. Your job is to review the document, identify any missing or non-compliant sections, and update it to fully align with the standard format and content requirements demonstrated in the attached reference SOPs.
|
||||
|
||||
## Analyze the Provided Document:
|
||||
|
||||
Identify the current structure, section headers, and content.
|
||||
Note any missing, incomplete, or non-standard sections.
|
||||
|
||||
## Remediate and Standardize:
|
||||
|
||||
Add any missing required sections (e.g., Purpose, Scope, Prerequisites, Procedure, Escalation, Definitions, Revision History).
|
||||
Ensure all section headers match the standard naming conventions.
|
||||
Reorganize content as needed to follow the logical flow of the reference SOPs.
|
||||
|
||||
Fill in missing content with clear, concise, and professional language. If information is unavailable, insert [Missing] as a placeholder.
|
||||
|
||||
## Formatting:
|
||||
|
||||
Use consistent markdown formatting for all headings, lists, and tables.
|
||||
Ensure clarity, readability, and adherence to the style guide.
|
||||
Output:
|
||||
|
||||
Return the fully remediated and standardized document in markdown format.
|
||||
|
||||
Clearly mark any sections where information could not be inferred with [Missing].
|
||||
|
||||
## Reference:
|
||||
Use the attached SOPs as your template for structure, section order, and content expectations.
|
||||
|
||||
---
|
||||
Acknowledge that you understand the task and are ready to review and standardize the provided SOP document.
|
||||
@@ -1,6 +0,0 @@
|
||||
1) Please review the attached folder's contents. Let the user know what you find. Do not make any changes.
|
||||
- If you don't know what folder to look at, just ask.
|
||||
|
||||
2) Summarize your findings from the folder. Wait the user's approval to continue.
|
||||
|
||||
3) With approval, convert what is there into the standard format. Do not summarize or reduce any content. Where possible, leave placeholder markers for screenshots that can be added later. Think step by step to complete this. Ask clarifying questions before you begin as needed.
|
||||
@@ -1,279 +0,0 @@
|
||||
---
|
||||
description: A guided prompt for users to create technical documentation using SOP or Install Guide templates, with dynamic audience capture, template selection, section-by-section guidance, formatting flexibility, and iterative review.
|
||||
---
|
||||
# Technical Documentation Construction Meta-Prompt
|
||||
|
||||
**Instructions:**
|
||||
|
||||
This prompt will guide you through the process of creating technical documentation. You will be asked to select a template, identify your audience, and contribute content for each section. Placeholder text will be provided where needed. The process is iterative—review and refine as you go.
|
||||
|
||||
---
|
||||
## Step 1: Capture Topic and Audience
|
||||
|
||||
- What is the topic of your documentation?
|
||||
- Who is the intended audience? (e.g., technical staff, end users, support team)
|
||||
|
||||
## Step 2: Select Documentation Template
|
||||
|
||||
- Choose the template that best fits your needs:
|
||||
- Standard Operating Procedure (SOP)
|
||||
- Installation Guide
|
||||
- Microsoft Document Type (e.g., Knowledge Article, How-To, FAQ)
|
||||
|
||||
## Step 3: Section-by-Section Guidance (Soft Gating)
|
||||
|
||||
For each section below, provide as much detail as possible. If unsure, use placeholder text and refine later.
|
||||
|
||||
### SOP Template Sections
|
||||
|
||||
1. **Purpose**: What is the goal of this SOP?
|
||||
2. **Scope**: What systems, teams, or processes does this SOP cover?
|
||||
3. **Roles and Responsibilities**: Who is involved and what are their duties?
|
||||
4. **Procedures**: List step-by-step instructions for the process.
|
||||
5. **Troubleshooting**: Common issues and solutions.
|
||||
6. **Compliance/Regulatory**: Any standards or policies to follow.
|
||||
7. **Revision History**: Track changes and updates.
|
||||
|
||||
### Install Guide Template Sections
|
||||
|
||||
1. **Introduction**: Brief overview of the installation.
|
||||
2. **Prerequisites**: What is required before starting?
|
||||
3. **Installation Steps**: Detailed, ordered instructions.
|
||||
4. **Verification**: How to confirm successful installation.
|
||||
5. **Troubleshooting**: Common installation problems and fixes.
|
||||
6. **Support/Contact**: Where to get help.
|
||||
7. **Revision History**: Track changes and updates.
|
||||
|
||||
### Microsoft Document Types (as applicable)
|
||||
|
||||
- **Knowledge Article**: Problem, Solution, Additional Resources
|
||||
- **How-To**: Task, Steps, Tips
|
||||
- **FAQ**: Question, Answer, Related Links
|
||||
|
||||
## Step 4: Iterative Review and Feedback
|
||||
|
||||
- After completing each section, review for clarity and completeness.
|
||||
- Solicit feedback from stakeholders or end users.
|
||||
- Update sections as needed and document changes in the Revision History.
|
||||
|
||||
## Step 5: Finalization and Publishing
|
||||
|
||||
- Ensure all sections are complete and accurate.
|
||||
- Format the document according to organizational standards (Markdown, Word, etc.).
|
||||
- Publish to the appropriate repository or knowledge base.
|
||||
|
||||
---
|
||||
|
||||
## Appendix A: Full SOP Template
|
||||
|
||||
```markdown
|
||||
---
|
||||
title: "[SOP Title Placeholder]"
|
||||
description: "[Brief description of the SOP]"
|
||||
type: "SOP"
|
||||
version: "[template]"
|
||||
author: "[Author/Team]"
|
||||
date: "[YYYY-MM-DD]"
|
||||
---
|
||||
|
||||
<!-- SOP Title and Logo Row -->
|
||||
<div style="display: flex; align-items: center; justify-content: space-between; margin-bottom: 1.5em;">
|
||||
<h1 style="margin: 0; font-size: 2em;">[SOP Title Placeholder]</h1>
|
||||
<img src="https://rwdn-uploads.s3.amazonaws.com/mcgl15001/production/54b7a8d305541296303508cec6e5dfb6.png" alt="Company Logo" style="height:60px; max-width:180px; object-fit:contain;">
|
||||
</div>
|
||||
|
||||
## Introduction
|
||||
|
||||
### Purpose
|
||||
|
||||
[State the purpose of this SOP.]
|
||||
|
||||
### Audience
|
||||
|
||||
[Who is this SOP for?]
|
||||
|
||||
### Scope
|
||||
|
||||
[What does this SOP cover?]
|
||||
|
||||
---
|
||||
|
||||
## Definitions
|
||||
|
||||
[Define any key terms or acronyms used in this SOP.]
|
||||
|
||||
---
|
||||
|
||||
## Prerequisites / Required Tools & Access
|
||||
|
||||
- [List required systems, permissions, or tools.]
|
||||
|
||||
---
|
||||
|
||||
## Procedure
|
||||
|
||||
### Step 0: Ticket Handling
|
||||
|
||||
[Describe how tickets should be received, validated, categorized, prioritized, and assigned before beginning technical steps. Include any scenario-based triage, required information, and communication guidelines.]
|
||||
|
||||
### Step 1: [Phase/Step Title]
|
||||
|
||||
[Describe the first step or phase.]
|
||||
|
||||
### Step 2: [Phase/Step Title]
|
||||
|
||||
[Describe the next step or phase.]
|
||||
|
||||
<!-- Repeat as needed for all steps -->
|
||||
|
||||
---
|
||||
|
||||
## Post-Procedure Actions
|
||||
|
||||
[List any follow-up actions, documentation, or verifications required.]
|
||||
|
||||
---
|
||||
|
||||
## Escalation Procedures
|
||||
|
||||
- [Describe what to do if something goes wrong or is out of scope.]
|
||||
|
||||
---
|
||||
|
||||
## References / Related Documents
|
||||
|
||||
- [Link to related SOPs, policies, or external resources.]
|
||||
|
||||
---
|
||||
|
||||
## Revision History
|
||||
|
||||
| Version | Date | Author | Description |
|
||||
| ------- | ---------- | ------------- | --------------------- |
|
||||
| Template | YYYY-MM-DD | [Author/Team] | Initial template |
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Appendix B: Full Install Guide Template
|
||||
|
||||
```markdown
|
||||
---
|
||||
title: "[Install Guide Title Placeholder]"
|
||||
description: "[Brief description of the install guide]"
|
||||
type: "Install Guide"
|
||||
version: "[template]"
|
||||
author: "[Author/Team]"
|
||||
date: "[YYYY-MM-DD]"
|
||||
---
|
||||
|
||||
<!-- Guide Title and Logo Row -->
|
||||
<div style="display: flex; align-items: center; justify-content: space-between; margin-bottom: 1.5em;">
|
||||
<h1 style="margin: 0; font-size: 2em;">[Install Guide Title Placeholder]</h1>
|
||||
<img src="https://rwdn-uploads.s3.amazonaws.com/mcgl15001/production/54b7a8d305541296303508cec6e5dfb6.png" alt="Company Logo" style="height:60px; max-width:180px; object-fit:contain;">
|
||||
</div>
|
||||
|
||||
<!-- Table of Contents (Optional: Remove if guide is short) -->
|
||||
## Table of Contents *(remove if not needed)*
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Definitions](#definitions)
|
||||
- [Prerequisites / Required Tools & Access](#prerequisites--required-tools--access)
|
||||
- [Installation Procedure](#installation-procedure)
|
||||
- [Post-Installation Actions](#post-installation-actions)
|
||||
- [Troubleshooting / Escalation Procedures](#troubleshooting--escalation-procedures)
|
||||
- [References / Related Documents](#references--related-documents)
|
||||
- [Revision History](#revision-history)
|
||||
|
||||
## Introduction
|
||||
|
||||
### Purpose
|
||||
|
||||
[State the purpose of this install guide.]
|
||||
|
||||
### Audience
|
||||
|
||||
[Who is this guide for? (e.g., end users, IT staff, installers)]
|
||||
|
||||
### Scope
|
||||
|
||||
[What does this guide cover? (e.g., product, system, or environment)]
|
||||
|
||||
---
|
||||
|
||||
## Definitions
|
||||
|
||||
[Define any key terms, acronyms, or product names used in this guide.]
|
||||
|
||||
---
|
||||
|
||||
## Prerequisites / Required Tools & Access
|
||||
|
||||
- [List required hardware, software, permissions, or tools.]
|
||||
|
||||
---
|
||||
|
||||
## Installation Procedure
|
||||
|
||||
### Step 1: Preparation
|
||||
|
||||
1. [Unpack all components and verify contents.]
|
||||
2. [Prepare the environment (e.g., clear workspace, check power/network access).]
|
||||
|
||||
> **Note:** Use semantic headings and provide alt text for all images/screenshots.
|
||||
|
||||
### Step 2: Physical/Software Installation
|
||||
|
||||
1. [Mount hardware, connect cables, or run the installer.]
|
||||
2. [Follow on-screen prompts or physical installation instructions.]
|
||||
|
||||
> **Warning:** [Call out any critical warnings, e.g., "Do not power on until all cables are connected."]
|
||||
|
||||
### Step 3: Configuration
|
||||
|
||||
1. [Set up network, create accounts, or adjust initial settings.]
|
||||
2. [Document any default credentials and prompt for change.]
|
||||
|
||||
### Step 4: Verification
|
||||
|
||||
1. [Verify installation by powering on, logging in, or running a test.]
|
||||
2. [Check for error messages or abnormal behavior.]
|
||||
|
||||
<!-- Add or remove steps as needed for your product/process -->
|
||||
|
||||
---
|
||||
|
||||
## Post-Installation Actions
|
||||
|
||||
- [List any follow-up actions, documentation, or verifications required after installation.]
|
||||
|
||||
---
|
||||
|
||||
## Troubleshooting / Escalation Procedures
|
||||
|
||||
| Issue | Resolution |
|
||||
| --- | --- |
|
||||
| [Example: Installer fails to launch] | [Check system requirements, run as administrator] |
|
||||
| [Example: Device not detected] | [Verify connections, check drivers] |
|
||||
|
||||
- [Add more issues and resolutions as needed.]
|
||||
|
||||
**Support Contact:** [Insert support email, phone, or ticketing system link.]
|
||||
|
||||
---
|
||||
|
||||
## References / Related Documents
|
||||
|
||||
- [Link to related guides, manuals, or support resources.]
|
||||
|
||||
---
|
||||
|
||||
## Revision History
|
||||
|
||||
| Version | Date | Author | Description |
|
||||
| ------- | ---------- | ------------- | --------------------- |
|
||||
| Template | YYYY-MM-DD | [Author/Team] | Initial template |
|
||||
```
|
||||
|
||||
---
|
||||
**Note:** This prompt is designed to be flexible and accessible. Use it as a living document—update and iterate as your process evolves.
|
||||
@@ -1,205 +0,0 @@
|
||||
You are given a well-formatted markdown file. Your task is to convert it into a modern, visually appealing HTML document. Follow these instructions:
|
||||
|
||||
1) Analyze the Markdown Structure:
|
||||
|
||||
- Identify all headings, lists, tables, code blocks, blockquotes, and other markdown elements.
|
||||
- Note the hierarchy and indentation to inform the HTML structure and CSS styling.
|
||||
|
||||
2) Generate HTML
|
||||
|
||||
- Convert each markdown element to its semantic HTML equivalent (e.g., # to <h1>, ## to <h2>, - to <ul><li>, etc.).
|
||||
- Convert Markdown image syntax (``) to HTML `<img>` tags, preserving the `src` and `alt` attributes, and apply modern styling (e.g., `max-width:100%; margin: 16px 0; border-radius: 4px;`).
|
||||
- Preserve the document’s logical structure and sectioning.
|
||||
|
||||
3) Apply Modern CSS
|
||||
|
||||
- Use a clean, modern font (e.g., 'Segoe UI', Arial, sans-serif).
|
||||
- Add a centered, card-like container with padding, rounded corners, and a subtle box-shadow.
|
||||
- Style headings with distinct colors and spacing for hierarchy.
|
||||
- Style lists, tables, and code blocks for clarity and readability.
|
||||
- Ensure responsive design for mobile devices.
|
||||
- Use the markdown’s own formatting (e.g., heading levels, list nesting, table presence) to influence spacing, font sizes, and section separation in the CSS.
|
||||
|
||||
4) Header Row
|
||||
|
||||
- At the top, include a header row with the document title (from the first heading) and a company logo (use a placeholder or provided URL).
|
||||
|
||||
5) Meta Information
|
||||
|
||||
- If the markdown includes frontmatter (YAML or similar), display all metadata fields found (not just title, description, version, author, date) in a styled block at the top. This ensures custom fields like `applies_to`, `issue`, or others are visible for KBAs/Guides.
|
||||
- If a `logo` field is present in the frontmatter, use its value as the logo URL in the header row; otherwise, use the default logo URL.
|
||||
- Use the YAML `title` as the main document title (`<h1>`). If both YAML and Markdown H1 exist, suppress the Markdown H1 in the HTML output to avoid duplicate titles.
|
||||
|
||||
|
||||
6) Accessibility & Best Practices
|
||||
|
||||
- Use semantic HTML tags.
|
||||
- Ensure sufficient color contrast and readable font sizes.
|
||||
- Add alt text for images.
|
||||
- If a blockquote starts with `Note:`, `Warning:`, or `Tip:`, add a CSS class and icon/color for visual distinction (e.g., blue for Note, yellow for Warning, green for Tip). This helps highlight important callouts in KBAs/Guides.
|
||||
- If multiple H1s or inline HTML are detected, warn or normalize as needed to maintain clean output.
|
||||
|
||||
|
||||
7) Output
|
||||
|
||||
- Return a complete HTML file with embedded CSS (in a <style> block in the <head>) in the "Documentation\HTML" folder.
|
||||
- Name the new file using the `type` and `title`from the frontmatter. Replace spaces with underscores and appending `.html` (e.g., `SOP_Escalation_Procedures.html`).
|
||||
- The HTML should be ready to use and visually modern, reflecting the structure and intent of the original markdown.
|
||||
- Ensure:
|
||||
- The meta block displays all frontmatter fields present.
|
||||
- Only one H1 (from YAML title) is rendered at the top.
|
||||
- Blockquotes with callout keywords are visually distinct.
|
||||
- The logo is sourced from frontmatter if available.
|
||||
- Optionally, output a warning if multiple H1s or inline HTML are found in the source.
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>[Document Title]</title>
|
||||
<style>
|
||||
/* Modern CSS based on markdown structure */
|
||||
body {
|
||||
font-family: 'Segoe UI', Arial, sans-serif;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
background-color: #f4f4f9;
|
||||
color: #333;
|
||||
}
|
||||
main {
|
||||
max-width: 800px;
|
||||
margin: 50px auto;
|
||||
padding: 20px;
|
||||
background: #fff;
|
||||
border-radius: 8px;
|
||||
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
|
||||
}
|
||||
.header-row {
|
||||
display: flex;
|
||||
justify-content: space-between;
|
||||
align-items: center;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
.header-row h1 {
|
||||
font-size: 28px;
|
||||
margin: 0;
|
||||
color: #0078d4;
|
||||
}
|
||||
.header-row img {
|
||||
max-height: 50px;
|
||||
}
|
||||
.meta {
|
||||
font-size: 14px;
|
||||
color: #666;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
h2, h3, h4 {
|
||||
color: #005a9e;
|
||||
}
|
||||
ul, ol {
|
||||
margin-left: 20px;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
code {
|
||||
font-family: 'Courier New', Courier, monospace;
|
||||
background-color: #eef;
|
||||
padding: 2px 4px;
|
||||
border-radius: 4px;
|
||||
}
|
||||
pre {
|
||||
background-color: #eef;
|
||||
padding: 10px;
|
||||
border-radius: 4px;
|
||||
overflow-x: auto;
|
||||
}
|
||||
table {
|
||||
width: 100%;
|
||||
border-collapse: collapse;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
th, td {
|
||||
border: 1px solid #ddd;
|
||||
padding: 8px;
|
||||
text-align: left;
|
||||
}
|
||||
th {
|
||||
background-color: #0078d4;
|
||||
color: white;
|
||||
}
|
||||
blockquote {
|
||||
margin: 0;
|
||||
padding: 10px 20px;
|
||||
background-color: #f9f9f9;
|
||||
border-left: 5px solid #0078d4;
|
||||
}
|
||||
/* Responsive design */
|
||||
@media (max-width: 600px) {
|
||||
.header-row {
|
||||
flex-direction: column;
|
||||
align-items: flex-start;
|
||||
}
|
||||
.header-row h1 {
|
||||
font-size: 24px;
|
||||
}
|
||||
.meta {
|
||||
font-size: 12px;
|
||||
}
|
||||
}
|
||||
|
||||
/* Dark mode support */
|
||||
@media (prefers-color-scheme: dark) {
|
||||
body {
|
||||
background-color: #181a1b;
|
||||
color: #e3e6eb;
|
||||
}
|
||||
main {
|
||||
background: #23272b;
|
||||
box-shadow: 0 4px 16px rgba(0,0,0,0.4);
|
||||
}
|
||||
.header-row h1 {
|
||||
color: #4fc3f7;
|
||||
}
|
||||
.meta {
|
||||
color: #b0b8c1;
|
||||
}
|
||||
h2, h3, h4 {
|
||||
color: #90caf9;
|
||||
}
|
||||
code, pre {
|
||||
background-color: #23272b;
|
||||
color: #e3e6eb;
|
||||
}
|
||||
table {
|
||||
background: #23272b;
|
||||
}
|
||||
th {
|
||||
background-color: #1565c0;
|
||||
color: #fff;
|
||||
}
|
||||
td {
|
||||
border-color: #333;
|
||||
}
|
||||
blockquote {
|
||||
background-color: #23272b;
|
||||
border-left: 5px solid #4fc3f7;
|
||||
}
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<main>
|
||||
<div class="header-row">
|
||||
<h1>[Document Title]</h1>
|
||||
</div>
|
||||
<div class="meta">
|
||||
<strong>Description:</strong> ...<br>
|
||||
<strong>Version:</strong> ...<br>
|
||||
<strong>Author:</strong> N. Castaldi<br>
|
||||
<strong>Date:</strong> ...
|
||||
</div>
|
||||
<!-- Converted markdown content here -->
|
||||
</main>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
@@ -1,168 +0,0 @@
|
||||
You are given a well-formatted markdown file. Your task is to convert it into a modern, visually appealing HTML document. Follow these instructions:
|
||||
|
||||
1) Analyze the Markdown Structure:
|
||||
|
||||
- Identify all headings, lists, tables, code blocks, blockquotes, and other markdown elements.
|
||||
- Note the hierarchy and indentation to inform the HTML structure and CSS styling.
|
||||
|
||||
2) Generate HTML
|
||||
|
||||
- Convert each markdown element to its semantic HTML equivalent (e.g., # to <h1>, ## to <h2>, - to <ul><li>, etc.).
|
||||
- Convert Markdown image syntax (``) to HTML `<img>` tags, preserving the `src` and `alt` attributes, and apply modern styling (e.g., `max-width:100%; margin: 16px 0; border-radius: 4px;`).
|
||||
- Preserve the document’s logical structure and sectioning.
|
||||
|
||||
3) Apply Modern CSS
|
||||
|
||||
- Use a clean, modern font (e.g., 'Segoe UI', Arial, sans-serif).
|
||||
- Add a centered, card-like container with padding, rounded corners, and a subtle box-shadow.
|
||||
- Style headings with distinct colors and spacing for hierarchy.
|
||||
- Style lists, tables, and code blocks for clarity and readability.
|
||||
- Ensure responsive design for mobile devices.
|
||||
- Use the markdown’s own formatting (e.g., heading levels, list nesting, table presence) to influence spacing, font sizes, and section separation in the CSS.
|
||||
|
||||
4) Header Row
|
||||
|
||||
- At the top, include a header row with the document title (from the first heading) and a company logo (use a placeholder or provided URL).
|
||||
|
||||
5) Meta Information
|
||||
|
||||
- If the markdown includes frontmatter (YAML or similar), display all metadata fields found (not just title, description, version, author, date) in a styled block at the top. This ensures custom fields like `applies_to`, `issue`, or others are visible for KBAs/Guides.
|
||||
- If a `logo` field is present in the frontmatter, use its value as the logo URL in the header row; otherwise, use the default logo URL.
|
||||
- Use the YAML `title` as the main document title (`<h1>`). If both YAML and Markdown H1 exist, suppress the Markdown H1 in the HTML output to avoid duplicate titles.
|
||||
|
||||
|
||||
6) Accessibility & Best Practices
|
||||
|
||||
- Use semantic HTML tags.
|
||||
- Ensure sufficient color contrast and readable font sizes.
|
||||
- Add alt text for images.
|
||||
- If a blockquote starts with `Note:`, `Warning:`, or `Tip:`, add a CSS class and icon/color for visual distinction (e.g., blue for Note, yellow for Warning, green for Tip). This helps highlight important callouts in KBAs/Guides.
|
||||
- If multiple H1s or inline HTML are detected, warn or normalize as needed to maintain clean output.
|
||||
|
||||
|
||||
7) Output
|
||||
|
||||
- Return a complete HTML file with embedded CSS (in a <style> block in the <head>) in the "Documentation\HTML" folder.
|
||||
- Name the new file using the `type` and `title`from the frontmatter. Replace spaces with underscores and appending `.html` (e.g., `SOP_Escalation_Procedures.html`).
|
||||
- The HTML should be ready to use and visually modern, reflecting the structure and intent of the original markdown.
|
||||
- Ensure:
|
||||
- The meta block displays all frontmatter fields present.
|
||||
- Only one H1 (from YAML title) is rendered at the top.
|
||||
- Blockquotes with callout keywords are visually distinct.
|
||||
- The logo is sourced from frontmatter if available.
|
||||
- Optionally, output a warning if multiple H1s or inline HTML are found in the source.
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<title>[Document Title]</title>
|
||||
<style>
|
||||
/* Modern CSS based on markdown structure */
|
||||
body {
|
||||
font-family: 'Segoe UI', Arial, sans-serif;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
background-color: #f4f4f9;
|
||||
color: #333;
|
||||
}
|
||||
main {
|
||||
max-width: 800px;
|
||||
margin: 50px auto;
|
||||
padding: 20px;
|
||||
background: #fff;
|
||||
border-radius: 8px;
|
||||
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
|
||||
}
|
||||
.header-row {
|
||||
display: flex;
|
||||
justify-content: space-between;
|
||||
align-items: center;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
.header-row h1 {
|
||||
font-size: 28px;
|
||||
margin: 0;
|
||||
color: #0078d4;
|
||||
}
|
||||
.header-row img {
|
||||
max-height: 50px;
|
||||
}
|
||||
.meta {
|
||||
font-size: 14px;
|
||||
color: #666;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
h2, h3, h4 {
|
||||
color: #005a9e;
|
||||
}
|
||||
ul, ol {
|
||||
margin-left: 20px;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
code {
|
||||
font-family: 'Courier New', Courier, monospace;
|
||||
background-color: #eef;
|
||||
padding: 2px 4px;
|
||||
border-radius: 4px;
|
||||
}
|
||||
pre {
|
||||
background-color: #eef;
|
||||
padding: 10px;
|
||||
border-radius: 4px;
|
||||
overflow-x: auto;
|
||||
}
|
||||
table {
|
||||
width: 100%;
|
||||
border-collapse: collapse;
|
||||
margin-bottom: 20px;
|
||||
}
|
||||
th, td {
|
||||
border: 1px solid #ddd;
|
||||
padding: 8px;
|
||||
text-align: left;
|
||||
}
|
||||
th {
|
||||
background-color: #0078d4;
|
||||
color: white;
|
||||
}
|
||||
blockquote {
|
||||
margin: 0;
|
||||
padding: 10px 20px;
|
||||
background-color: #f9f9f9;
|
||||
border-left: 5px solid #0078d4;
|
||||
}
|
||||
/* Responsive design */
|
||||
@media (max-width: 600px) {
|
||||
.header-row {
|
||||
flex-direction: column;
|
||||
align-items: flex-start;
|
||||
}
|
||||
.header-row h1 {
|
||||
font-size: 24px;
|
||||
}
|
||||
.meta {
|
||||
font-size: 12px;
|
||||
}
|
||||
}
|
||||
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<main>
|
||||
<div class="header-row">
|
||||
<h1>[Document Title]</h1>
|
||||
<img src="https://rwdn-uploads.s3.amazonaws.com/mcgl15001/production/54b7a8d305541296303508cec6e5dfb6.png" alt="Company Logo" style="height:60px; max-width:180px; object-fit:contain;">
|
||||
</div>
|
||||
<div class="meta">
|
||||
<strong>Description:</strong> ...<br>
|
||||
<strong>Version:</strong> ...<br>
|
||||
<strong>Author:</strong> ...<br>
|
||||
<strong>Date:</strong> ...
|
||||
</div>
|
||||
<!-- Converted markdown content here -->
|
||||
</main>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
@@ -1,21 +0,0 @@
|
||||
Role: You are a Senior Proposal Manager and RFP Analyst with 15 years of experience in winning high-value contracts.
|
||||
|
||||
Task: Conduct a comprehensive review of the attached RFP documentation to extract key requirements, identify risks, and summarize the project scope.
|
||||
|
||||
Instructions:
|
||||
|
||||
Executive Summary: Provide a 3-sentence high-level overview of what the client is looking for.
|
||||
|
||||
Key Requirements: Extract a bulleted list of mandatory technical and functional requirements.
|
||||
|
||||
Critical Deadlines: List all dates (submission, Q&A period, demos) in a table format.
|
||||
|
||||
Gap/Risk Analysis: Identify any areas where the documentation is vague or where we might face significant delivery risks.
|
||||
|
||||
Technical Constraints: If any files are unreadable or corrupted, list them immediately by filename and specify the required format (e.g., PDF, .docx, .xlsx).
|
||||
|
||||
Constraints: > * Base your answers only on the provided files.
|
||||
|
||||
If information is missing, state "Information not found in provided documents" rather than guessing.
|
||||
|
||||
Use a professional, objective tone.
|
||||
@@ -1,17 +0,0 @@
|
||||
"I am working with the Frank Meadows agentic framework to prepare a sensitive production script for my public GitHub portfolio. I need to perform a Sanitization and Atomic Refactor of the attached RBAC Governance script.
|
||||
|
||||
The Objectives:
|
||||
|
||||
Data Masking: Replace all internal company names, tenant IDs, specific Entra ID (Azure AD) group names, and API keys with generic placeholders.
|
||||
|
||||
Security Hardening: Ensure the script uses environment variables (e.g., os.getenv or $env:) instead of hardcoded credentials.
|
||||
|
||||
Validation Check: Ensure the logic includes error-handling for API timeouts or 'not found' objects, as per the Frank Meadows core directives.
|
||||
|
||||
The Workflow Instructions:
|
||||
|
||||
Gated Workflow: Do NOT output the entire scrubbed script at once. We will move through the script in functional blocks.
|
||||
|
||||
Atomic Edits: For each block, provide the refactored code and wait for my 'Approved' or 'Modify' signal before moving to the next block.
|
||||
|
||||
The First Gate: Please acknowledge these constraints and ask me to provide the first block of code (Imports and Connection/Authentication logic) to begin the sanitization process."
|
||||
Reference in New Issue
Block a user