first commit, minimal config and styling

Author: serverless-mom

package-lock.json

@@ -1,13 +1,10 @@
 ---
-import FormattedDate from './FormattedDate.astro';
-
 export interface Props {
   post: {
     slug: string;
     data: {
       title: string;
       description?: string;
-      pubDate: Date;
       author?: string;
       tags?: string[];
       image?: string;
@@ -23,19 +20,16 @@ const isExternal = !!post.data.externalLink;
 ---
 
 <article class="post on-list">
-  <h2 class="post-title">
+  <h2 class="post-title" style="padding-top: 15px;">
     <a href={postUrl} target={isExternal ? "_blank" : undefined} rel={isExternal ? "noopener" : undefined}>
       {post.data.title}
     </a>
   </h2>
-  <div class="post-meta">
-    <time class="post-date">
-      <FormattedDate date={post.data.pubDate} />
-    </time>
-    {post.data.author && (
+  {post.data.author && (
+    <div class="post-meta">
       <span class="post-author">{post.data.author}</span>
-    )}
-  </div>
+    </div>
+  )}
   {post.data.tags && post.data.tags.length > 0 && (
     <span class="post-tags">
       {post.data.tags.map((tag, index) => (
@@ -52,12 +46,16 @@ const isExternal = !!post.data.externalLink;
   )}
   {post.data.description && (
     <div class="post-content">
-      <p>{post.data.description}</p>
+      <p>
+        <a href={postUrl} target={isExternal ? "_blank" : undefined} rel={isExternal ? "noopener" : undefined}>
+          {post.data.description}
+        </a>
+      </p>
     </div>
   )}
   <div>
     <a href={postUrl} class="read-more button inline" target={isExternal ? "_blank" : undefined} rel={isExternal ? "noopener" : undefined}>
-      [Read more]
+      See the prompt
     </a>
   </div>
 </article>

public/cover.svg

@@ -1,18 +1,17 @@
 import { defineCollection, z } from 'astro:content';
 
-const posts = defineCollection({
+const library = defineCollection({
   type: 'content',
   schema: z.object({
     title: z.string(),
     description: z.string().optional(),
-    pubDate: z.coerce.date(),
-    updatedDate: z.coerce.date().optional(),
     author: z.string().optional(),
     image: z.string().optional(),
+    icon: z.string().optional(),
     externalLink: z.string().optional(),
     tags: z.array(z.string()).default([]),
     draft: z.boolean().default(false),
   }),
 });
 
-export const collections = { posts };
+export const collections = { library };

public/favicon.ico

@@ -0,0 +1,41 @@
+---
+title: API Network Interception
+description: A guide for intercepting and analyzing API network requests with Playwright.
+icon: 🌐
+tags: ["AI", "Checkly"]
+---
+
+If you’re monitoring back end APIs or performing request interception, it can be useful to know exactly what APIs the page relies on. Use the following prompt to analyze network traffic with your AI agent.
+
+```markdown
+You are a Playwright network analysis expert specializing in TypeScript, frontend development, and Playwright end-to-end testing.
+
+You are given a scenario and need to perform network analysis on a web page to identify API dependencies and network behavior.
+
+## Instructions
+
+- Use the tools provided by the Playwright MCP server to navigate to the specified website
+- Monitor and intercept all network requests during page load and user interactions
+- Analyze the network traffic to identify:
+  - API endpoints being called
+  - Request methods (GET, POST, PUT, DELETE, etc.)
+  - Response status codes and timing
+  - Request/response headers and payloads
+  - Third-party services and external dependencies
+- Categorize network calls by type (API calls, static assets, analytics, etc.)
+- Identify any failed requests or performance bottlenecks
+- Only after completing the analysis, provide a comprehensive report of all API dependencies and network behavior
+
+## Analysis Output
+
+Provide the following information:
+1. **API Endpoints**: List all API calls with methods and response codes
+2. **External Dependencies**: Third-party services, CDNs, analytics
+3. **Performance Metrics**: Request timing and any slow-loading resources
+4. **Error Analysis**: Failed requests and potential issues
+5. **Security Observations**: Any insecure requests or potential vulnerabilities
+
+## User Input
+
+Analyze the network traffic and API dependencies of [YOUR-WEBSITE].com
+```