How to Use Kitchen Equipment Guides in HowToCook: Air Fryer and Pressure Cooker Documentation

The HowToCook repository hosts comprehensive Markdown-based kitchen equipment guides in the tips/learn/ directory, providing detailed operational workflows, safety protocols, and temperature-time specifications for modern appliances like air fryers and high-pressure cookers.

The Anduin2017/HowToCook project organizes culinary knowledge as static Markdown content, making it accessible for both direct reading and programmatic integration. Its kitchen equipment guides eliminate operational guesswork through standardized workflows, physics explanations, and safety checklists structured for immediate practical application.

Repository Structure for Equipment Documentation

The HowToCook repository employs a hierarchical file system where appliance-specific documentation resides in specialized subdirectories. The root level contains categories like dishes/, starsystem/, and tips/, with the latter housing all technique and equipment-focused content.

Within tips/learn/, each appliance receives a self-contained Markdown file following a consistent heading hierarchy (#, ##, ###). This architecture enables static site generators to parse the content while allowing direct linking via GitHub blob URLs.

Key equipment guide files include:

• tips/learn/空气炸锅.md – Complete air fryer documentation including theory, workflow, and cooking matrices
• tips/learn/高压力锅.md – High-pressure cooker guide emphasizing safety protocols and operational constraints

Navigating the Air Fryer Guide

The air fryer documentation (tips/learn/空气炸锅.md) provides end-to-end coverage from thermodynamic principles to specific ingredient settings. The guide structures information into logical segments: device description, working principles, advantages over conventional frying, step-by-step workflows, safety considerations, and data-driven cooking recommendations.

Temperature-Time Reference Tables

A critical component of the air fryer guide is its parameterized cooking table, which eliminates trial-and-error for common ingredients. The repository maintains this data in standard Markdown table format, allowing direct embedding into recipe pages or extraction via parsing tools.

## 空气炸锅常用食材温度‑时间表

| 食材   | 温度 (℃) | 时间 (分钟) | 关键步骤 |
|--------|----------|-------------|----------|
| 薯条   | 200      | 15-20       | 每 5 分钟摇晃一次 |
| 鸡翅   | 180      | 18-22       | 表面刷蜂蜜水 |
| 鱼类   | 180-190  | 12-15       | 中途翻面一次 |
| 牛排   | 200      | 8-12        | 每面 4-6 分钟 |
| 蛋挞   | 170-180  | 12-15       | 不预热直接烤 |

Each entry specifies exact Celsius temperatures, time ranges, and technique annotations (such as shaking intervals or flipping requirements) derived from empirical testing documented in the repository's collaborative workflow.

Using the Pressure Cooker Documentation

The high-pressure cooker guide (tips/learn/高压力锅.md) follows an identical structural pattern but emphasizes safety-critical operational constraints unique to pressurized cooking. Beyond standard workflow descriptions, the documentation highlights specific hazards including foam overflow, liquid maximum-fill limits, and pressure-release protocols.

Safety-First Content Architecture

According to the source code analysis of the repository structure, the pressure cooker guide explicitly addresses:

• Foam hazards: Warnings regarding foaming ingredients that can clog steam valves
• Liquid limits: Maximum fill thresholds to prevent dangerous pressure buildup
• Thermal dynamics: Explanations of how pressure affects boiling points and cooking acceleration

These sections use hierarchical headers to separate theoretical explanations from actionable safety checklists, ensuring users understand both the "how" and the "why" of critical precautions.

Integration Methods for Developers

Because HowToCook stores these guides as static Markdown without proprietary formatting, they integrate seamlessly into external documentation systems, mobile applications, or static site generators.

Direct Markdown Linking

The simplest consumption method references the canonical GitHub URLs within other Markdown documents:

想要快速了解空气炸锅的使用方法，请参考完整指南：

[空气炸锅使用手册](https://github.com/Anduin2017/HowToCook/blob/master/tips/learn/空气炸锅.md)

同理，使用高压锅时请阅读：

[高压锅使用手册](https://github.com/Anduin2017/HowToCook/blob/master/tips/learn/高压力锅.md)

This approach leverages the repository's file-path-as-identifier architecture, ensuring stable links that remain valid across repository updates.

Programmatic Content Fetching

For applications requiring embedded equipment data, the raw GitHub content API provides direct access to guide text. The following Node.js implementation demonstrates fetching both guides at build time for static site generation:

import fetch from 'node-fetch';
const AIR_FRYER_URL = 'https://raw.githubusercontent.com/Anduin2017/HowToCook/master/tips/learn/空气炸锅.md';
const PRESSURE_URL = 'https://raw.githubusercontent.com/Anduin2017/HowToCook/master/tips/learn/高压力锅.md';

async function getGuide(url) {
  const res = await fetch(url);
  if (!res.ok) throw new Error(`Failed to fetch ${url}`);
  return await res.text();   // markdown content
}

// Usage
(async () => {
  const airFryerGuide = await getGuide(AIR_FRYER_URL);
  const pressureGuide = await getGuide(PRESSURE_URL);
  console.log(airFryerGuide.slice(0, 200)); // preview
})();

This method returns pure Markdown content suitable for rendering with libraries like marked or remark, allowing developers to present HowToCook's kitchen equipment guides within custom user interfaces while maintaining the original hierarchical structure.

Summary

• Kitchen equipment guides reside in tips/learn/ as static Markdown files with consistent ATX-style headings, enabling both human reading and programmatic parsing.
• The air fryer guide (tips/learn/空气炸锅.md) contains empirical temperature-time tables for ingredients ranging from fries to egg tarts, with specific technique annotations.
• Pressure cooker documentation (tips/learn/高压力锅.md) prioritizes safety protocols, detailing liquid limits and foam hazards critical for safe operation.
• Content is accessible via stable GitHub blob URLs or raw content endpoints, supporting direct linking or API-based integration into third-party applications.
• The repository's hierarchical structure allows contributors to add new appliance guides by creating Markdown files under tips/learn/ following the established heading patterns.

Frequently Asked Questions

Where are the kitchen equipment guides located in the HowToCook repository?

The guides are located in the tips/learn/ directory of the Anduin2017/HowToCook repository. Specific files include 空气炸锅.md for air fryer documentation and 高压力锅.md for pressure cooker instructions, both stored as static Markdown files with standardized heading hierarchies.

What safety information does the pressure cooker guide include?

According to the tips/learn/高压力锅.md source file, the guide includes critical safety warnings about foam accumulation that can clog steam valves, strict liquid maximum-fill limits to prevent pressure buildup, and detailed pressure-release protocols. These sections appear under dedicated safety headers separate from operational workflows.

How can I programmatically access the air fryer temperature tables?

You can fetch the raw Markdown content using the GitHub raw content API endpoint: https://raw.githubusercontent.com/Anduin2017/HowToCook/master/tips/learn/空气炸锅.md. The temperature tables appear as standard Markdown pipe tables within the content, parseable using regular expressions or Markdown AST parsers like remark or markdown-it.

Can I contribute new kitchen equipment guides to the repository?

Yes, contributors can add new appliance guides by creating Markdown files in the tips/learn/ directory following the established structure: device description, working principles, advantages, safety notes, and operational workflows. The repository accepts pull requests that maintain the consistent heading hierarchy and file naming conventions used in existing guides like 空气炸锅.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}